Book a call Free rebuild

HTTP/2

August 24, 2022 Updated November 16, 2026 2 min read

Performance glossaryHTTP/2 is the 2015 version of the web's transfer protocol. It sends many requests over one connection at once, which makes pages with many files load faster.

HTTP/2 is the second major version of HTTP, the protocol browsers and servers use to exchange pages, images, scripts, and everything else on the web. It was published as a standard in May 2015, building on Google's experimental SPDY protocol. It changed how data moves without changing what it means: URLs, methods, status codes, and headers work exactly as before.

The problem with HTTP/1.1

Under HTTP/1.1, a connection carries one request and response at a time. To fetch several files at once, browsers open several connections to the same server, typically up to six, and requests queue behind slow ones. A modern page with dozens or hundreds of files spends much of its time waiting in those queues. Developers worked around this by combining files, using image sprites, and spreading assets across several domains.

How HTTP/2 works

  • Multiplexing. Many requests and responses travel over a single connection at the same time, split into small frames and interleaved, so one slow file no longer holds up the rest.
  • Binary framing. Messages are sent in a compact binary format instead of plain text, which is quicker and less error-prone to parse.
  • Header compression. HPACK compresses the headers that repeat on every request, such as cookies and the user agent string.
  • Prioritization. The browser can signal which resources matter most, such as CSS before images.

HTTP/2 also defined server push, which let a server send files before the browser asked for them. It was rarely a net win in practice, and Chrome dropped support for it during 2022. Preload hints (<link rel="preload">) and the 103 Early Hints response cover the same need.

What it means for a site

With HTTP/2, many small files are cheap, so the old HTTP/1.1 workarounds matter less, and some, such as spreading files across extra domains, now do harm by forcing extra connections. Combining files can still help when a page has a very large number of tiny files, but it is no longer essential.

HTTP/2 does not make a page lighter or a slow server faster; it removes a bottleneck in delivering many files. Nor does it affect rankings directly: Googlebot has been able to crawl over HTTP/2 since November 2020, but Google has said there is no ranking benefit from it.

How to enable it

Browsers only use HTTP/2 over HTTPS, so a site needs a valid SSL/TLS certificate first. After that, it is a server setting. Nearly all hosts and CDNs enable HTTP/2 by default, and on a self-managed server it is switched on in the nginx, Apache (mod_http2), or LiteSpeed configuration. WordPress itself needs no changes.

To check, open the browser's developer tools, go to the Network tab, right-click the column headers to add the Protocol column, and reload. Requests served over HTTP/2 show h2.

What came next

HTTP/2 still runs over TCP, so a single lost packet stalls every stream on the connection until it is resent. HTTP/3 moves to QUIC, over UDP, to remove that limitation.

Source: RFC 9113: HTTP/2.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.