Chapter 6. Optimizing for HTTP/2

 

This chapter covers

  • What HTTP/2 changes for web developers
  • Whether HTTP/1.1 web performance techniques are antipatterns under HTTP/2
  • Other performance techniques and whether they’re still relevant under HTTP/2
  • How to optimize for HTTP/1 and HTTP/2
  • Connection coalescing

You’ve gained a good understanding of HTTP/2: what it aims to solve and how it works, and some of the new features and opportunities it brings. I still have some more advanced topics to cover in the third part of this book, but you’ve enough information to look at what HTTP/2 means for your websites and how you can optimize for it. How should you change your development practices? Can you drop some performance techniques? What new techniques can you use? What do you do for those users who can’t use HTTP/2? This chapter aims to answer those questions.

6.1. What HTTP/2 means for web developers

You’ve seen that HTTP/2 fundamentally changes how HTTP messages are sent to servers, and should bring performance benefits as a result. But do developers need to change their development languages and practices? Should you use particular Java-Script frameworks to take advantages of HTTP/2? On the whole, the answer to these questions is that no changes are required, though some may be beneficial.

6.2. Are some HTTP/1.1 optimizations now antipatterns?

6.3. Web performance techniques still relevant under HTTP/2

6.4. Optimizing for both HTTP/1.1 and HTTP/2

Summary

sitemap