Explainers · Explainer
What Is HTTP/3? A Plain Explanation
Short answer
HTTP/3 is the newest version of the protocol that delivers web pages, published as RFC 9114 in June 2022. It runs HTTP over QUIC, a UDP-based transport with TLS 1.3 built in, instead of TCP. That change removes TCP head-of-line blocking, so one lost packet stalls only the stream it belongs to, cuts new connection setup to 1 round trip, and leaves your WordPress content unchanged.
Key takeaways
- HTTP/3 is HTTP over QUIC, published as RFC 9114 in June 2022, with the same methods, status codes, and headers as HTTP/2.
- QUIC runs on UDP with TLS 1.3 built in, so a new connection takes 1 round trip and a return visit can take 0.
- One lost packet stalls only its own stream under HTTP/3, while under HTTP/2 over TCP it stalls every stream.
- W3Techs counted HTTP/3 on 40.8% of websites in November 2026, while Can I Use put browser support at 94.55%.
- Most WordPress sites get HTTP/3 by turning it on at a CDN such as Cloudflare, with no plugin or theme change.
- If a network blocks UDP, browsers fall back to HTTP/2 on their own, so enabling HTTP/3 rarely breaks a visit.
What is HTTP/3?
HTTP/3 is the newest version of the web protocol that carries pages from your server to a visitor's browser, running over QUIC instead of TCP.
The Internet Engineering Task Force published it as RFC 9114 in June 2022. The QUIC transport it runs on became RFC 9000 in May 2021.
Your WordPress pages, images, and files travel the same way as before. HTTP/3 changes the delivery road, not the cargo.
How is HTTP/3 different from HTTP/2?
HTTP/3 keeps the same requests, status codes, and headers as HTTP/2 and changes only the transport layer underneath them.
HTTP/2 runs over TCP, and TCP delivers bytes in strict order. If one packet is lost, every later packet waits until the lost one is sent again, so a single loss stalls all streams on the connection. That stall is called head-of-line blocking.
HTTP/3 runs over QUIC, which gives each stream its own ordered byte sequence. A lost packet affects only the streams whose data was in that packet, and the rest keep moving. The HTTP/3 explained guide describes this as the core fix QUIC brings.
Header compression changes too. HTTP/3 uses QPACK instead of the HPACK used by HTTP/2. QPACK has 99 entries in its static table, against 61 for HPACK, and it works when streams arrive out of order.
| Version | Published | Transport | Header compression |
|---|---|---|---|
| HTTP/1.1 | 1997 | TCP | None |
| HTTP/2 | 2015 | TCP + TLS | HPACK |
| HTTP/3 | June 2022 | QUIC over UDP + TLS 1.3 | QPACK |
What is QUIC and why does HTTP/3 use it?
QUIC is a transport protocol built on UDP that adds its own reliability, ordering, and encryption instead of borrowing them from TCP.
Google began developing QUIC in 2012, and Chrome shipped an experimental version in 2013. The IETF chartered a working group to standardise it in October 2016, and the name HTTP/3 was adopted in November 2018.
QUIC folds the transport and encryption handshakes into one step. TLS 1.3 is built into QUIC, so there is no plain-text HTTP/3 and no separate TLS layer to set up.
QUIC also guards against abuse. A server must not send more than 3 times the data it received to an unverified address, and the first packet must be padded to at least 1,200 bytes. Those limits keep the protocol from being used to flood a victim.
How does HTTP/3 make pages load faster?
HTTP/3 cuts the wait before the first byte by setting up an encrypted connection in 1 round trip instead of 2, and in 0 round trips for a returning visitor.
A round trip is one message out and one message back. TCP needs its own handshake before TLS can even start, so a new TCP plus TLS 1.3 connection takes 2 round trips. QUIC combines both handshakes, so the request can go out after 1.
| Connection | Round trips before the request |
|---|---|
| TCP + TLS 1.2, new | 3 |
| TCP + TLS 1.3, new | 2 |
| TCP + TLS 1.3, resumed with 0-RTT | 1 |
| QUIC, new | 1 |
| QUIC, resumed with 0-RTT | 0 |
The gains show up most on bad networks. Google reported 8% faster mean search latency on desktop and 3.6% on mobile from QUIC, with the slowest 1% of connections loading a full second faster. Wix reported around a third faster connection setup with double-digit LCP gains at the 75th percentile.
Connection migration helps mobile visitors too. QUIC identifies a connection by an ID, not by the IP address and port, so a phone that switches from cellular to Wi-Fi can keep the same connection instead of starting over.
On a fast, clean wired connection, the gain is small. HTTP/3 raises the floor for the worst connections more than it lifts the ceiling for the best ones.
Does HTTP/3 change what your WordPress site sends?
No. HTTP/3 does not change your content, your theme, your plugins, or your HTML.
WordPress itself does not handle the protocol. Your server or CDN decides which HTTP version a visitor gets, and WordPress just hands over the same pages. That is why speed work on WordPress still starts with caching, images, and hosting, not with the protocol.
Each request still gets its own stream. Servers are expected to allow at least 100 concurrent request streams, so a page with many images, scripts, and stylesheets does not queue up behind one slow file.
How many websites and browsers use HTTP/3?
W3Techs counted HTTP/3 on 40.8% of websites in November 2026, so it is common but far from universal.
Browser support is far ahead of site support. Can I Use put global HTTP/3 browser support at 94.55% as of October 2026. Chrome 87 and later, Edge 87 and later, Firefox 88 and later, and Safari 16 and later all ship it by default.
The gap has a simple cause. A browser can add HTTP/3 in an update, but a website needs a server, host, or CDN that offers it. Many sites still sit on older setups, so their visitors keep using HTTP/2 even though their browsers are ready.
How do you check if your WordPress site uses HTTP/3?
Open Chrome DevTools, go to the Network tab, add the Protocol column, and look for h3 next to your requests.
- Open your site in Chrome and press F12, or Ctrl+Shift+I on Windows and Linux.
- Click the Network tab and reload the page.
- Right-click any column header and tick Protocol.
- Look for h3 on your main page and asset requests. h2 means HTTP/2 and http/1.1 means HTTP/1.1.
Check on a second visit, not just the first. Browsers learn about HTTP/3 from an Alt-Svc header the server sends, so the first visit often still loads over HTTP/2 and later visits switch to h3.
You can also paste your domain into http3check.net, a free checker that reports whether a site answers over QUIC. If it says no, your server or CDN has not turned HTTP/3 on yet.
How do you enable HTTP/3 on WordPress?
The easiest route for most WordPress sites is a CDN, and Cloudflare offers HTTP/3 on all plans, including Free, as of November 2026.
Cloudflare's own docs give these steps:
- Log in to the Cloudflare dashboard and select your site.
- Go to Speed, then Settings.
- Open Protocol Optimization.
- Switch HTTP/3 to On.
You need an SSL certificate at Cloudflare's edge for the toggle to work. The Cloudflare HTTP/3 docs list HTTP/3 as available on Free, Pro, Business, and Enterprise plans.
If you would rather not use a CDN, ask your host first. Some managed WordPress hosts already run HTTP/3 on their servers, and some do not. Our guide to choosing WordPress hosting explains what to ask before you sign up.
A CDN is the cheaper path for most small sites. CDN pricing for WordPress starts low, and Cloudflare's free plan already covers HTTP/3.
What happens if a visitor's network blocks HTTP/3?
Nothing breaks. The browser falls back to HTTP/2 or HTTP/1.1 on its own.
QUIC runs on UDP port 443, and some corporate networks, firewalls, and public Wi-Fi setups block or throttle UDP. When that happens, the browser notices the QUIC attempt failing and retries over TCP, so the visitor still sees your site.
Cloudflare's troubleshooting docs note that some networks do not fully support QUIC over UDP. If a visitor reports odd SSL errors, you can switch HTTP/3 off briefly to test, then switch it back on after the test.
This fallback is why enabling HTTP/3 is low risk. You are adding a faster path, not removing the old one, and TCP port 443 stays open for visitors who need it.
What myths about HTTP/3 should you ignore?
The biggest myth is that HTTP/3 doubles the speed of every site.
- Myth: HTTP/3 makes every site much faster. The gains depend on the network. Lossy mobile links gain the most, and fast wired links gain little.
- Myth: HTTP/3 replaces HTTPS. It does not. TLS 1.3 is built into QUIC, and you still need a certificate. Our guide to SSL certificate costs covers what that costs.
- Myth: you must rebuild your WordPress site. You do not. HTTP/3 is a server or CDN setting, and your theme and plugins stay untouched.
- Myth: HTTP/3 works without a certificate. It does not. Cloudflare requires an SSL certificate at its edge before HTTP/3 can be switched on.
What mistakes should you avoid?
Do not treat HTTP/3 as a fix for a slow site.
- Turning HTTP/3 on and then closing TCP port 443. Older browsers and blocked networks still need TCP, so keep the fallback.
- Judging it from one first visit. Browsers need the Alt-Svc header before they try h3, so check a repeat visit in DevTools.
- Paying for a new host just for HTTP/3. A CDN in front of your current host usually adds it for less.
- Ignoring the real bottlenecks. Slow PHP, uncached pages, and huge images hurt far more than the protocol choice, and HTTP/3 will not hide them.
Frequently asked questions
Does HTTP/3 replace HTTPS?
No. HTTP/3 still encrypts everything, because TLS 1.3 is built into QUIC itself. You still need a valid SSL certificate on your server or CDN, and visitors still see the padlock. The difference is where the encryption lives, not whether it exists.
Will HTTP/3 make my WordPress site faster?
It can help, mostly for visitors on mobile or lossy networks, where one lost packet no longer stalls every download and connections set up in 1 round trip. On fast wired connections the gain is small. Slow hosting, uncached pages, and heavy images matter far more than the protocol version.
Do I need a plugin to use HTTP/3 on WordPress?
No. WordPress does not handle the HTTP version, so no plugin is needed. Your host, server, or CDN turns HTTP/3 on. For most small sites the simplest path is a CDN in front of the site, which adds HTTP/3 without touching WordPress at all.
Why does my site still show h2 in DevTools?
Browsers learn about HTTP/3 from an Alt-Svc header sent on an earlier visit, so the first load often still uses HTTP/2. Reload the page or visit a second time and check the Protocol column again. If it still shows h2, your server or CDN has probably not enabled HTTP/3 yet.
What if my host does not offer HTTP/3?
Put a CDN that supports HTTP/3 in front of your site. The CDN talks HTTP/3 to visitors while your origin server keeps using HTTP/2 or HTTP/1.1. Cloudflare offers HTTP/3 on all plans including Free, so this costs nothing extra for most small sites.
Is HTTP/3 safe to turn on?
Yes, for most sites. Browsers fall back to HTTP/2 automatically when a network blocks UDP, so visitors are not locked out. If one visitor reports odd connection errors, you can switch HTTP/3 off briefly to test whether it is the cause, then switch it back on.
Sources
- HTTP/3 explained http.dev
- HTTP/3 (with QUIC) Cloudflare Docs
- RFC 9114: HTTP/3 RFC Editor
- Usage statistics of HTTP/3 for websites W3Techs
- HTTP/3 browser support Can I Use
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
