HTTP/2 vs HTTP/1.1 (and HTTP/3): What Changed and Why Sites Are Faster

In February 2015 the HTTP/2 standard was finalised, the first major update to the web’s core protocol since HTTP/1.1 in 1999. We said then that it would make the web faster, and it did. Here’s a clear look at HTTP/2 vs HTTP/1.1, what HTTP/3 has added since, and what it means for your site in 2026.

Quick answer: HTTP/2 sends many requests at once over a single connection (multiplexing), compresses headers and uses a binary format, so pages with lots of files load faster than with HTTP/1.1. HTTP/3 keeps those ideas but runs over QUIC instead of TCP, which helps on slow or mobile networks. Most hosts and CDNs now support both; your site just needs HTTPS.

HTTP/2 vs HTTP/1.1: key differences

• Multiplexing: HTTP/1.1 handles one request at a time per connection, so browsers open several connections. HTTP/2 sends many requests in parallel over one connection.
• Header compression: HTTP/2 uses HPACK to shrink repeated headers like cookies.
• Binary framing: HTTP/2 uses binary frames instead of plain text, which is faster to parse.
• Stream priority: browsers can signal which resources matter most.
• Server push: part of the original spec, but rarely helpful. Chrome removed support in 2022, so don’t rely on it.

HTTP/2 grew out of Google’s SPDY protocol, and browsers only use it over HTTPS.

What HTTP/3 adds

HTTP/3 (standardised in 2022) runs over QUIC, a protocol built on UDP. It avoids TCP’s head-of-line blocking, sets up secure connections faster and handles switching networks (Wi-Fi to mobile) better. All major browsers support it, and CDNs like Cloudflare enable it with a toggle.

What changes for website owners

• Old HTTP/1.1 tricks like domain sharding and combining every file into one are less important now.
• Serve your site over HTTPS; HTTP/2 and HTTP/3 need it in browsers.
• Use a host or CDN with HTTP/2 and HTTP/3 enabled; LiteSpeed, Nginx and Apache all support HTTP/2.
• Keep optimising: fewer heavy scripts, compressed images and deferring non-critical CSS still matter.

How to check which protocol your site uses

1. Open Chrome DevTools (F12) > Network.
2. Right-click the column headers and enable Protocol.
3. Reload: h2 means HTTP/2, h3 means HTTP/3.

Then measure speed with these web page speed tests. Technical details are in the HTTP/2 specification (RFC 9113) (external site).

FAQ

Is HTTP/2 faster than HTTP/1.1?

Usually yes, especially for pages with many images, scripts and stylesheets.

Do I need to change my website for HTTP/2?

No code changes are needed. Your server or CDN handles it once HTTPS is set up.

Should I enable HTTP/3?

Yes, if your host or CDN offers it. Browsers fall back to HTTP/2 automatically.