HTTP/3 and QUIC: is it worth switching on for your site?
Short answer: HTTP/3 is the newest version of the protocol browsers use to load websites. It runs over QUIC, a transport built on UDP, and mainly helps visitors on patchy mobile and wireless connections. For most small business sites, the easiest and safest way to get it is to switch it on at your CDN, where it is often a single setting, while your server keeps using HTTP/1.1 or HTTP/2 behind it. Do not expect it to fix a slow site on its own; images, scripts and server response times still matter far more.
What HTTP/3 changes
Every version of HTTP keeps the same basic meaning: requests, responses, status codes and headers. What changes is how those messages travel. HTTP/1.1 and HTTP/2 run over TCP. HTTP/3, standardised in RFC 9114, runs over QUIC, which RFC 9000 describes as a UDP-based, multiplexed and secure transport.
RFC 9114's abstract summarises why QUIC is attractive for HTTP: stream multiplexing, per-stream flow control and low-latency connection establishment. In plainer terms:
- No head-of-line blocking at the transport layer. With HTTP/2 over TCP, one lost packet can stall every file on the connection until it is resent. Cloudflare's documentation explains that QUIC solves TCP's head-of-line blocking problem, so performance over lossy networks can be better.
- Faster connection setup. QUIC combines transport and encryption setup, and RFC 9000 describes an option for clients to send data immediately (0-RTT) when they have connected before.
- Connection migration. RFC 9000 explains that QUIC connections are not strictly bound to a single network path, and connection migration lets them move to a new one. That helps a phone that switches from Wi-Fi to mobile data mid-visit.
Who actually benefits
The gains are largest for visitors on unreliable networks: mobile users on trains, rural connections, crowded venue Wi-Fi and customers browsing from abroad. On a fast, stable office connection the difference may be hard to measure.
That makes HTTP/3 a reasonable improvement for businesses whose customers browse on phones in the field, such as trades, hospitality, events and delivery services. It is not a substitute for basic performance work.
How browsers find HTTP/3
Browsers do not try HTTP/3 blindly. They usually connect over HTTP/2 or HTTP/1.1 first and learn that HTTP/3 is available from the server. RFC 9114 describes how an origin can advertise an equivalent HTTP/3 endpoint using the Alt-Svc response header with the "h3" token. MDN's Alt-Svc reference shows the header's format, with a protocol identifier, the alternative host and port, and an optional ma value giving how long the advertisement can be cached.
Because of this, the first visit may use HTTP/2 and later requests switch to HTTP/3. It also means there is a built-in fallback: if UDP traffic is blocked, as on some corporate networks, browsers simply keep using HTTP/2.
Option one: switch it on at your CDN
If your site already sits behind a CDN, this is usually the simplest route. Cloudflare's documentation, for example, says HTTP/3 is available on all its plans, requires an SSL certificate at its edge, and is enabled from the dashboard. It also notes that HTTP/3 between Cloudflare and your origin server is not yet supported, so the CDN talks HTTP/3 to visitors and an older version to your server. Other CDNs and many managed hosts offer similar switches.
That split is fine. The benefits of QUIC are greatest on the last mile to the visitor, which is exactly the part the CDN handles.
Option two: enable it on your own server
Some web servers and proxies now support HTTP/3 directly, but it involves more moving parts:
- Your server software and its TLS library must support QUIC.
- Firewalls and load balancers must allow UDP on port 443, not just TCP.
- You must send the Alt-Svc header so browsers know to try it.
- Monitoring and logging tools need to understand the new traffic.
For a typical business site, this effort rarely pays off compared with a CDN setting. It can make sense for apps that serve large numbers of mobile users directly from their own infrastructure.
Checking that it works
After enabling it, open your browser's developer tools, look at the Network panel and add the Protocol column. Reload the page a couple of times; you should see "h3" for requests to your domain. Online HTTP/3 checkers can also confirm the Alt-Svc header and a working QUIC connection.
Then measure. Compare real-user performance data, especially for mobile visitors, over a few weeks before and after. If nothing changed, that is useful information too: it tells you your visitors' connections were not the bottleneck.
What to fix first
If your site is slow, HTTP/3 should come after the basics:
- Oversized images and missing compression.
- Too many third-party scripts.
- Slow server response times and no caching.
- Render-blocking fonts and styles.
These usually dwarf any protocol-level gain. A quick audit with your browser's performance tools or a page-speed report will show where the time actually goes, and that list is a better guide to your next change than any protocol setting.
A worked example
Consider a hypothetical Glasgow food-truck business whose customers check locations and pre-order on their phones, often from busy streets with weak signal. The site already used a CDN for images.
The owner's developer switched on HTTP/3 at the CDN, confirmed "h3" in the browser's network panel and left the origin server unchanged. Over the following month, real-user data showed modestly faster loads for mobile visitors on slow connections and no change on desktop. The bigger win that month came from compressing menu photos, which the developer tackled alongside.
FAQ
Can HTTP/3 break my site?
Rarely. Browsers fall back to HTTP/2 when HTTP/3 does not work, so visitors still load the site.
Does HTTP/3 help SEO?
Not directly. Faster, more reliable loading helps visitors, which is what matters.
Do I still need HTTPS?
Yes. QUIC is encrypted by design, and HTTP/3 requires a valid certificate.
If you're wondering whether HTTP/3 or other speed changes are worth it for your site, send us your address and what feels slow.