The limitations of HTTP/1.X forced us to develop various application workarounds (sharding, concatenation, spriting, inlining, etc.) to optimize performance. However, in the process we’ve also introduced numerous regressions: poor caching, unnecessary downloads, delayed execution, and more.
HTTP/2 eliminates the need for these hacks and allows us to both simplify our applications and deliver improved performance – a rare combination! In this session we’ll take a critical look at how the current best practices came to be; the new features of HTTP/2 that make them obsolete; and what you need to do to deliver the optimal HTTP/2 experience:
- Why you should unshard, unconcat, and unsprite your assets
- Why you should switch from inlining to server push
- What to look for in an HTTP/2 server for optimal performance
- What new best practices are possible with HTTP/2
… plus other hands-on tips for getting the most out of HTTP/2 both on the server and the client.
Ilya Grigorik is a web performance engineer and developer advocate at Google, where his focus is on making the web fast and driving adoption of performance best practices.
Comments on this page are now closed.