Blog / How the internet works /

HTTP/2 and HTTP/3 explained

Every time you open a web page, your browser and a server hold a short conversation. The browser asks for the page, the server answers, and then the browser asks for the images, the stylesheet, the scripts and the fonts. The rules of that conversation are called HTTP, and the version in use affects how quickly your site feels.

Most people never think about it. But if you run a website, you have probably seen “HTTP/2” or “HTTP/3” in a hosting plan, a speed test or a Cloudflare setting, and wondered if it matters.

Short answer: yes, a bit, and usually you only need to check that it is switched on.

The plain-words version

  • HTTP/1.1 is the old way. Reliable, but it handles requests a little like a single till at a shop. One customer at a time per line, and browsers worked around the queue by opening several lines.
  • HTTP/2 (standardised in 2015) opens one connection and sends many requests down it at once. One till, but it serves lots of people in turn without anyone having to wait for the whole of someone else’s big order.
  • HTTP/3 (standardised in 2022) changes the road underneath. It runs over a protocol called QUIC, built on UDP instead of TCP, and copes better when the connection is shaky.

What HTTP/2 changed

A typical page needs dozens of files. Under HTTP/1.1, browsers opened a handful of connections in parallel and queued the rest. Web developers adapted: they combined all their CSS into one big file, glued images into sprites and spread files over several domains to get more connections.

HTTP/2 made much of that unnecessary:

  • Multiplexing. Many requests share a single connection at the same time.
  • Header compression. The repeated chatter that comes with every request is squeezed down.
  • Encryption in practice. The standard allows plain connections, but browsers only support HTTP/2 over HTTPS, so moving to HTTPS is the entry ticket. If that is new to you, HTTPS and the padlock covers the basics.

One consequence: old advice such as “combine every file into one” matters less than it used to. Fewer, sensibly sized files are still good, but you do not need to contort your site for it.

The catch HTTP/2 left behind

HTTP/2 still sits on TCP. TCP guarantees that data arrives in order, and that creates a problem called head-of-line blocking. If one packet gets lost, everything behind it waits while it is resent, even if those later packets belong to a different file.

On a steady fibre connection you rarely notice. On a patchy mobile connection, switching between Wi-Fi and data, or moving between towers, you notice a lot. That is the situation many people browse in, especially on phones in places where the signal drifts.

What HTTP/3 does differently

HTTP/3 swaps TCP for QUIC. In short:

  • Streams are independent. A lost packet only holds up its own file, not the whole page.
  • Faster start. Connections can be set up with fewer back-and-forth trips, which helps when the first request is the slow one.
  • Better with moving networks. QUIC can survive a change of network without starting again from scratch.

You will usually hear this described as helping most on slow, lossy or changing connections. On a fast, stable line, the gap between HTTP/2 and HTTP/3 is small. I would be wary of anyone promising big speed jumps from switching it on.

Does it matter for SEO?

Indirectly. Google does not rank pages for “using HTTP/3”. But speed feeds into user experience and into things like Core Web Vitals, and faster connections help with how quickly the first content appears. Your biggest wins still come from images, scripts and server response time. Protocol upgrades are the cherry, not the cake.

How to check what your site uses

  1. Open your site in Chrome, then open DevTools and go to the Network tab.
  2. Right-click the column headings and tick Protocol.
  3. Reload. You will see h2 for HTTP/2 and h3 for HTTP/3.

Prefer not to open DevTools? Several free online “HTTP/3 test” tools will tell you from a URL.

How to get it

The good news is it is rarely your job to install anything.

  • Hosting. Most modern hosts serve HTTP/2 by default on HTTPS sites. HTTP/3 depends on the host’s server software. Check your plan’s documentation or ask support. Do not assume.
  • Cloudflare. If your site sits behind Cloudflare, visitors connect to Cloudflare first, and it supports HTTP/2 and HTTP/3. There is a setting to turn HTTP/3 on. Your own server can stay on whatever it supports, because the connection from Cloudflare to your server is separate. More on that setup in Cloudflare settings that help speed and security.
  • A CDN generally. A CDN is often the easiest route to the latest protocol, because the CDN’s job is to keep up with this stuff.

A browser always picks the best protocol both sides support, and falls back quietly if one is missing. So turning HTTP/3 on is low risk. Nothing breaks for visitors on older setups.

Common myths

  • “HTTP/2 needs me to rebuild my site.” No. It works with the same HTML, CSS and images.
  • “HTTP/3 will fix a slow site.” If your page is slow because of a 4 MB hero image or twelve plugins, the protocol will not save you.
  • “Bundling everything is now wrong.” Not wrong, just less necessary.

Key takeaways

  • HTTP is the language browsers and servers use. HTTP/2 and HTTP/3 are newer, faster versions.
  • HTTP/2 handles many requests at once over one connection. HTTP/3 does it over QUIC and copes better with weak networks.
  • Check the Protocol column in Chrome DevTools to see which one you have.
  • A host or a CDN such as Cloudflare is the easiest way to turn them on.
  • Fix heavy images and scripts first; treat the protocol as a bonus.

Have you ever looked at the Protocol column on your own site? Go and check. It takes thirty seconds, and it might tell you something your hosting plan never did.