Performance glossaryHTTP/3 is the latest version of the web's transfer protocol. It runs over QUIC instead of TCP, which speeds up connections and copes better with poor networks.
HTTP/3 is the third major version of HTTP, standardized as RFC 9114 in June 2022. It keeps the same meaning as earlier versions (URLs, methods, status codes, and headers are unchanged) but replaces the transport underneath. Where HTTP/1.1 and HTTP/2 run over TCP, HTTP/3 runs over QUIC, a transport protocol built on UDP that Google began developing and the IETF standardized in May 2021.
Why move away from TCP
HTTP/2 sends many requests over one TCP connection. TCP delivers data strictly in order, so if one packet is lost, everything behind it waits until it is resent, even data belonging to unrelated files. This is head-of-line blocking, and it hurts most on mobile networks and patchy Wi-Fi, where packet loss is common.
QUIC handles each stream independently. A lost packet only delays the stream it belongs to, and the other files keep arriving.
What HTTP/3 improves
- Faster connection setup. QUIC builds TLS 1.3 encryption into its own handshake, so a new connection is ready in one round trip instead of the two or more that TCP plus TLS needs. That shortens Time to First Byte on first visits, and returning visitors can sometimes send data immediately (0-RTT).
- No transport-level head-of-line blocking, as described above.
- Connection migration. A QUIC connection is identified by an ID rather than by IP address and port, so it can survive a phone switching from Wi-Fi to mobile data.
- Encryption by default. There is no unencrypted HTTP/3.
The gains are largest on slow, distant, or unreliable connections. On a fast, stable wired connection, HTTP/3 and HTTP/2 perform much the same.
How browsers switch to HTTP/3
Unless the site publishes a DNS HTTPS record that lists HTTP/3, a browser cannot know in advance that a server speaks it, so a first visit usually starts on HTTP/2. The server then advertises HTTP/3 in an Alt-Svc response header, and the browser uses it for later requests. With an HTTPS record, supporting browsers can use HTTP/3 from the first request. If a network blocks UDP, browsers fall back to HTTP/2 automatically.
Enabling HTTP/3 for a WordPress site
As with HTTP/2, nothing changes in WordPress: HTTP/3 is a server and network setting. The simplest route is a CDN, since Cloudflare and other major CDNs offer HTTP/3 to visitors whatever the origin server runs. LiteSpeed supports it natively, and recent versions of nginx include an HTTP/3 module. Apache does not support HTTP/3 on its own, so Apache-hosted sites usually get it through a CDN. Any firewall in front of the server must allow UDP traffic on port 443.
To check, open the Network tab in the browser's developer tools, add the Protocol column, and reload the page more than once. Requests over HTTP/3 show h3.