HTTP/3 in practice

A new transport underneath

HTTP/3 keeps the same request and response semantics developers already know, but it runs over QUIC instead of TCP. QUIC is built on UDP and moves connection management, encryption, and loss recovery into a single protocol. Most of the benefits show up on exactly the networks where the web has always struggled: mobile, lossy, and high latency.

Faster connection setup

A traditional HTTPS connection needs a TCP handshake followed by a TLS handshake. QUIC combines them, so a new connection is ready after one round trip, and a returning visitor can sometimes send data in the very first packet. On a link with 150 milliseconds of round-trip time, saving one or two trips is immediately noticeable.

No more head-of-line blocking

HTTP/2 multiplexed many requests over a single TCP connection, which was a large improvement, but it inherited a weakness. When one TCP packet was lost, every stream on the connection waited for its retransmission, even streams whose data had arrived intact. QUIC tracks loss per stream, so a lost packet carrying part of an image does not stall the stylesheet arriving alongside it.

Connection migration

A phone that moves from Wi-Fi to cellular gets a new IP address. With TCP, every open connection breaks and must be rebuilt. QUIC identifies connections by an ID rather than by address, so the connection can survive the switch. For someone walking out of a building while a page loads, this is the difference between a smooth load and a stalled one.

What to expect

The gains are uneven:

• On fast, stable desktop connections, the difference is often small.
• On mobile networks with packet loss, improvements of 10 to 20 percent in page load are common.
• For visitors far from your servers, the faster handshake matters most.

Enabling it

Most major CDNs support HTTP/3 with a configuration switch. Browsers discover support through the Alt-Svc header on an earlier response, so the first visit typically uses HTTP/2 and later requests upgrade. Some corporate networks block UDP entirely; browsers fall back to HTTP/2 automatically, so enabling HTTP/3 carries little risk.

Measuring the effect

Compare field metrics before and after enabling it, segmented by connection type. Look especially at the slowest quartile of visits, where the protocol's strengths show up. Do not expect a dramatic shift in median numbers on a site whose audience is mostly on fast office networks.

The bigger picture

HTTP/3 is not a substitute for sending fewer bytes. It makes the network more forgiving, but a page that needs four megabytes and sixty requests is still slow on any protocol.