HTTP/2 and HTTP/3

HTTP/2 and HTTP/3 are newer versions of HTTP, the protocol browsers and servers use to request and send web pages. They let many files travel over a single connection at once and reduce connection delays, which makes pages load more efficiently than the older HTTP/1.1.

Written by Paul Hoda, SEO consultant since 2005. Last updated 8 November 2026.

The problem with HTTP/1.1

Under HTTP/1.1, each connection handles one request at a time. Browsers worked around this by opening several connections per site, and developers combined files and used tricks like image sprites to cut the number of requests. A page with dozens of images, stylesheets and scripts still spent a lot of time waiting in queues.

What HTTP/2 changed

  • Multiplexing: many requests and responses share one connection at the same time, so files no longer queue behind each other.
  • Header compression: repeated request headers are compressed, saving data on every request.
  • Binary format: messages are more efficient for machines to process.

In practice, browsers only use HTTP/2 over HTTPS, so a secure site is a prerequisite.

What HTTP/3 adds

HTTP/3 runs over QUIC, a transport protocol built on UDP rather than TCP. QUIC combines connection setup and encryption into fewer round trips, so the first connection is faster. It also avoids a problem where one lost packet holds up every file on the connection, which helps on patchy mobile networks. Switching between Wi-Fi and mobile data can keep the connection alive rather than starting again.

Why they matter for SEO

Faster, more efficient connections help page speed, particularly on pages that load many separate files.

HTTP/3 can also shorten Time to First Byte on first visits by cutting connection setup.

Both feed into Core Web Vitals and user experience.

On crawling, Google announced in 2020 that Googlebot can crawl over HTTP/2 when a site supports it and it looks beneficial. Google has said this does not give a ranking boost; the benefit is more efficient crawling and lower server load. There is no need to request it.

How to enable and check them

  1. Make sure the whole site runs on HTTPS.
  2. Check whether your host or server already supports HTTP/2. Most modern hosting does by default.
  3. Enable HTTP/3 in your server or, more simply, through a CDN that supports it.
  4. Open browser developer tools, add the Protocol column in the Network tab, and look for h2 or h3.

Common misconceptions

  • Upgrading the protocol does not fix heavy pages: oversized images and scripts still need attention.
  • Old HTTP/1.1 tricks such as bundling every file into one giant file are less useful now and can even waste data on pages that use only part of it.
  • You do not need to change URLs, redirects or content to move to a newer protocol: the switch happens at server level and is invisible to visitors.
  • HTTP/3 falls back gracefully, so browsers that do not support it simply use HTTP/2.

Key Takeaways

  • HTTP/2 and HTTP/3 are faster successors to HTTP/1.1.
  • HTTP/2 sends many files over one connection at the same time.
  • HTTP/3 uses QUIC to cut connection delays and cope with poor networks.
  • Googlebot can crawl over HTTP/2, but Google says it is not a ranking boost.
  • Most hosts and CDNs can enable both with little effort.

Related Terms

Not sure how your own site measures up? Request a free SEO review, or keep learning in the SEO Encyclopedia.