HTTP/2, CSS/JS concatenation and Autoptimize

The web performance world is abuzz with HTTP/2, which should (among other improvements) do away with the latency that each separate HTTP-request introduces, thus rendering aggregation of e.g. CSS & JS an anti-pattern. But there’s at least one in depth facts and figures based article that is not ready to dismiss “packaging” just yet. So: testing, testing, testing!

Autoptimize will in the not too distant future very likely have a “don’t aggregate, just minimize”-option, but the proof of the pudding will always be in the eating testing; sometimes it will be better to aggregate and minify as we do now, sometimes only minifying will be the better approach. And maybe (often?) a combination of those will make most sense: suppose you have a site on which 90% of pages share 90% of JS code. In that case it will likely (testing, testing, testing!) help performance to aggregate & minify the 90% of JS while excluding all other JS from aggregation (and minifying that). Sounds like the new whitelist-filters in Autoptimize’s API will come in handy no? ;-)

5 thoughts on “HTTP/2, CSS/JS concatenation and Autoptimize

  1. Pingback: 17 Ways to Reduce Load Time - Search Engine Optimization

  2. Pingback: How to Speed up WordPress 17 Ways to Reduce Load Time | SandeKennedy ™

  3. Pingback: How to Speed up WordPress | Thanh Huynh - Web Developer

  4. Pingback: How to Speed up WordPress - 17 Best Tips to Improve Speed

  5. Pingback: How to Speed up WordPress – BloggingWin

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.