Comments on The Best Request Is No Request, Revisited

6 Reader Comments

Back to the Article
  1. we will have to revise our best practices with http/2, thank you for these precious elements !

    Copy & paste the code below to embed this comment.
  2. Great article. So, the sit tight and wait/don’t spend any money on the site won out in the end!

    CDN’s such as Cloudflare, are offering http/2 for free already. Splitting css to a page requirement level is an interesting idea - thought about this in ExpressionEngine after Greg Woods advocated editorial design a few years back - additional css can be added in easily at page level as an editorial piece in the CMS.

    Copy & paste the code below to embed this comment.
  3. This is exactly what we all need “Only transfer what your users actually need. Nothing more, nothing less”. - amazing article.

    Copy & paste the code below to embed this comment.
  4. Well written and well explained

    Copy & paste the code below to embed this comment.
  5. It goes without saying that even if you split up your resources, make sure those resources are on the same hostname/CDN otherwise the browser has to make another, expensive DNS lookup and connection negating http2’s multiplexing.

    As mentioned in the article, I would imagine if you have a bunch of javascript that needs to execute together, it makes no difference whether you split it up or not since one file is going to require another anyway (you can’t execute your JS if the lib or view files you’re using aren’t downloaded yet).

    Would be interesting to see if these findings also hold up on mobile, where resources (ram, processor, disk) aren’t as abundant.

    As always test and retest to see what works for your own site.

    Copy & paste the code below to embed this comment.
  6. Very informative article! Keep it up. Guest Post

    Copy & paste the code below to embed this comment.
  7. Sorry, commenting is closed on this article.