We recently published an introduction to HTTP/2 and how it’s likely to change our approach to web performance optimisation. In this post, we look at a very specific aspect of HTTP/2: server push.
HTTP/2 is a new protocol for communicating over the web. Its predecessor, HTTP/1.1, dates back to 1999 and is long overdue for retirement.
HTTP/2 is also here, now. There are already a number of server implementations, and it is fully supported in Chrome, Firefox and Opera (with support in IE11 on Windows 10). It’s worth noting that while the HTTP/2 spec doesn’t require encryption, current browser implementations only support it over TLS.
Why do we need HTTP/2? How does it differ from HTTP/1.1? And what will it mean for web performance?