When it comes to developing web sites and web applications, there are two things that developers always consider as it relates to the project’s assets and its performance:
- The number of HTTP requests a page requires
- Loading all of the assets versus only what we need for a page (also known as YAGNI or You ain’t gonna need it.)
This is an obvious problem as we have tools like Head.js and Sprockets for managing this issue, and then we have customizers for larger utilities like Bootstrap that allow us to customize our builds.
Managing WordPress assets is becoming incredibly more relevant especially as frameworks, themes, and plugins become more powerful, and as people begin to build full applications on top of WordPress.