Speed & performance · Explainer
HTTP/2 vs HTTP/3 for WordPress Sites
Short answer
HTTP/2 runs over TCP, while HTTP/3 runs over QUIC on UDP. That change matters most when packets are lost, because QUIC lets one stream stall without holding back the others. For most WordPress sites, HTTP/3 is worth enabling when your host or CDN offers it, and HTTP/2 stays a fine fallback when it does not.
Key takeaways
- HTTP/2 runs over TCP, while HTTP/3 runs over QUIC on UDP, which is the core difference.
- HTTP/3 removes TCP head-of-line blocking, so one lost packet stalls only its own stream.
- In 2025, Cloudflare saw 50% of requests on HTTP/2, 29% on HTTP/1.x and 21% on HTTP/3.
- Cloudflare offers HTTP/3 on all plans when an SSL certificate is present at its edge.
- LiteSpeed turns QUIC on by default, but UDP port 443 must be open for it to work.
- WordPress does not set the protocol itself; your server or CDN decides between HTTP/2 and HTTP/3.
What is the core difference between HTTP/2 and HTTP/3?
HTTP/2 runs over TCP, while HTTP/3 runs over QUIC on UDP.
That one change in transport explains almost every other difference. HTTP/2 and HTTP/3 carry the same kind of requests, responses, headers and status codes. They differ in how those messages travel across the network.
HTTP/3 is defined in RFC 9114, published in June 2022. The standard describes HTTP/3 as a mapping of HTTP semantics over QUIC, with stream multiplexing, per-stream flow control and low-latency connection setup. If you want the short version first, read What Is HTTP/3?.
How does HTTP/2 work?
HTTP/2 sends many requests and responses over one TCP connection at the same time.
It splits each message into small binary frames, tags each frame with a stream number, and interleaves frames from different streams. That method is called multiplexing. It fixed the HTTP/1.1 problem where responses had to arrive in order on each connection.
HTTP/2 was first published in May 2015 as RFC 7540 and revised in June 2022 as RFC 9113, according to MDN's history of HTTP. It also compresses headers with HPACK, which cuts repeated header data such as cookies.
The limit sits one layer down. TCP delivers one ordered byte stream, so a lost packet can hold back later bytes until the missing packet is resent. Those later bytes may belong to other HTTP/2 streams, yet they still wait.
How does HTTP/3 work?
HTTP/3 carries the same HTTP messages over QUIC instead of TCP.
QUIC is a multiplexed transport protocol that runs on UDP. It handles encryption, loss recovery and stream multiplexing itself, rather than leaving those jobs to TCP and a separate TLS layer. Each QUIC stream has its own loss recovery.
MDN explains that HTTP/3 uses QUIC over UDP instead of TCP, which reduces latency and removes the head-of-line blocking problem in HTTP. If a packet is lost, only the stream whose packets were lost is blocked. Other streams keep moving.
HTTP/3 also changes header compression. It uses QPACK, defined in RFC 9204 in June 2022, instead of HPACK. QPACK is built to work with QUIC streams without reintroducing the same blocking problem.
How do HTTP/2 and HTTP/3 compare side by side?
The table below shows the main differences in one place.
| Feature | HTTP/2 | HTTP/3 |
|---|---|---|
| Transport | TCP | QUIC over UDP |
| Standard | RFC 9113, June 2022 | RFC 9114, June 2022 |
| Multiplexing | Yes, over one TCP connection | Yes, over QUIC streams |
| Lost packet effect | Can stall all streams on the connection | Stalls only its own stream |
| Header compression | HPACK | QPACK |
| Encryption | TLS over TCP | Built into QUIC |
| Connection setup | TCP plus TLS handshakes | Fewer round trips with QUIC |
| Fallback | Used when HTTP/3 is not offered | Falls back to HTTP/2 or HTTP/1.1 |
Both versions need HTTPS in browsers. Neither version changes your WordPress content, your theme or your plugins. The change is in delivery, not in what visitors see on the page.
Which is faster for a WordPress site?
HTTP/3 is faster mainly on slow, lossy or mobile networks, not on every connection.
On a stable, low-loss connection, HTTP/2 and HTTP/3 often load a WordPress page in similar time. The page still needs the same HTML, CSS, images and scripts, and the server still needs the same time to build the page. Protocol choice does not fix a slow theme or a slow database query.
The gap opens when packets drop. Cloudflare Radar notes that QUIC lets HTTP/3 mitigate the effects of packet loss, set up connections more quickly and provide encryption by default. That is why mobile visitors, visitors far from your server and visitors on weak Wi-Fi tend to gain most.
Adoption data shows HTTP/2 still carries more traffic. In 2025, Cloudflare Radar reported that 50% of requests to Cloudflare used HTTP/2, 29% used HTTP/1.x and 21% used HTTP/3, for the period from 1 January to 2 December 2025. HTTP/3 is common, but it is not yet the default for most requests.
For a fuller view of speed work beyond the protocol, see How to Speed Up WordPress.
When should you pick HTTP/2?
Pick HTTP/2 when your host or CDN does not offer HTTP/3, or when HTTP/3 keeps failing on your network.
HTTP/2 is a safe, widely supported choice. It gives you multiplexing and header compression without any UDP requirement. Most hosts, CDNs and browsers support it, and it works through firewalls that block UDP.
You should also stay on HTTP/2 while you fix a broken HTTP/3 setup. A site that loads well on HTTP/2 beats a site that stalls while QUIC is half set up. Check the firewall, the certificate and the server settings first, then try HTTP/3 again.
HTTP/2 is also enough for many small sites on stable networks. If your visitors are mostly on desktop broadband near your server, the gain from HTTP/3 may be small. Other speed work, such as caching and image size, will usually matter more.
When should you pick HTTP/3?
Pick HTTP/3 when your host or CDN offers it and your visitors use mobile or distant networks.
HTTP/3 fits sites with many mobile visitors, visitors across countries and visitors on trains, cafes or weak home Wi-Fi. Those networks lose packets more often, and that is where per-stream recovery helps. It also fits sites where visitors switch networks, since QUIC is built to handle connection changes better than TCP.
WooCommerce stores and membership sites can gain too, but only if the rest of the stack is sound. HTTP/3 does not fix slow checkout code, uncached pages or a host that is short on PHP workers. Treat it as one layer of speed work, not as a fix on its own.
Enable HTTP/3 when it costs nothing extra and needs no server rebuild. That is the case for many Cloudflare and LiteSpeed setups described below. If enabling it needs a new server, a plan change or custom firewall work, weigh that cost against the likely gain for your visitors.
How do you enable HTTP/3 on WordPress?
You enable HTTP/3 at the server or CDN, not inside WordPress itself.
WordPress does not choose the HTTP version. Your web server or CDN decides which protocol to offer, and the browser picks the best version both sides support. A plugin cannot add HTTP/3 to a server that lacks it.
Cloudflare
Cloudflare offers HTTP/3 on all plans when an SSL certificate is present at its edge, according to Cloudflare's HTTP/3 docs. To turn it on, go to Speed, then Settings, then Protocol Optimization, and set HTTP/3 to On.
That setting covers the visitor-to-Cloudflare connection. Cloudflare does not use HTTP/3 to your origin server, so your origin can stay on HTTP/2.
LiteSpeed
LiteSpeed Web Server supports HTTP/3, and QUIC is on by default, according to LiteSpeed's docs. You need HTTPS with a trusted certificate, and UDP port 443 must be open at the firewall.
QUIC is supported in LiteSpeed Web Server 5.2 and later, and HTTP/3 support was introduced in July 2019. If you use LiteSpeed Cache, pair this with How to Set Up LiteSpeed Cache with QUIC.cloud.
Other hosts
Ask your host two questions before you change anything.
- Does this plan support HTTP/3, and is it already on?
- Is UDP port 443 open for my site?
If the answer to either question is no, ask what plan or setting change is needed. Do not edit server files or firewall rules you do not understand. A wrong firewall change can block visitors, while a wrong server setting can take the site down.
How do you check which protocol your site uses?
Open Chrome DevTools, load your site and look at the Protocol column in the Network tab.
Requests marked h3 use HTTP/3, h2 use HTTP/2 and http/1.1 use HTTP/1.1. If you do not see the Protocol column, right-click a column heading in the Network tab and turn it on. Load the page twice, since the first load may still use HTTP/2 while the browser learns that HTTP/3 is offered.
You can also check the response headers. Look for an alt-svc header that mentions h3, such as alt-svc: h3=“:443”.
That header tells the browser that an HTTP/3 endpoint exists for the site. Its absence does not always mean HTTP/3 is off, since some setups advertise it in DNS instead.
Check a few page types, not just the home page. Your home page may load over h3 while a checkout page or an admin page loads over h2. That split is normal when different parts of the site take different paths.
What does HTTP/3 cost?
HTTP/3 usually costs nothing extra when your host or CDN already supports it.
Cloudflare includes HTTP/3 on all plans, including its free plan, when an SSL certificate is present at the edge. LiteSpeed includes QUIC and HTTP/3 in the server software, with no separate HTTP/3 fee named in its docs. In both cases, the cost is the hosting or CDN plan you already pay for.
Costs appear only when your current setup lacks support. That can mean a host upgrade, a move to a CDN, or paid help to open UDP port 443 and set up the server. Ask for the price before you move, and check whether the new plan changes renewal pricing.
Do not pay for HTTP/3 alone. If a host charges extra just for the protocol toggle, compare the full plan first. Hosting speed depends on many factors, and How Hosting Affects WordPress Speed explains what else to check.
What is the verdict for different types of WordPress sites?
The best choice depends on your visitors and your setup, not on the version number alone.
| Site type | Verdict as of November 2026 |
|---|---|
| Small blog on stable broadband | HTTP/2 is enough; enable HTTP/3 only if it is free and simple |
| Blog with many mobile readers | HTTP/3 is worth enabling when your host or CDN offers it |
| WooCommerce store | Enable HTTP/3, but fix caching and checkout speed first |
| Membership or course site | Enable HTTP/3 for mobile members; keep HTTP/2 as fallback |
| Site behind Cloudflare | Turn HTTP/3 on in Cloudflare; no origin change is needed |
| Site on LiteSpeed hosting | Check UDP port 443, then let QUIC run by default |
| Site on old shared hosting | Stay on HTTP/2 until the host adds HTTP/3 support |
The HTTP Archive Web Almanac 2024 found that 26% of desktop pages and 28% of mobile pages signalled HTTP/3 support through alt-svc, up from 20% and 21% in 2023. Support is rising, but HTTP/2 still serves most home pages. That matches the Cloudflare traffic split above.
Use HTTP/3 as the preferred version and HTTP/2 as the fallback. Browsers fall back on their own when QUIC is blocked, so enabling HTTP/3 does not cut off visitors on older networks. For Core Web Vitals work that pairs with this choice, see How to Pass Core Web Vitals in WordPress.
What mistakes should you avoid?
Do not assume HTTP/3 will fix a slow site on its own.
- Enabling HTTP/3 while your pages are uncached, your images are large or your host is overloaded leaves the main problem in place.
- Blocking UDP port 443 at the firewall while turning HTTP/3 on at the server, so browsers never reach the QUIC endpoint.
- Turning HTTP/3 on at Cloudflare and expecting it to reach your origin, when Cloudflare uses HTTP/2 or HTTP/1.1 for that leg.
- Judging the change from one page load, since the first load may use HTTP/2 before the browser learns about HTTP/3.
- Paying for a plan upgrade only for HTTP/3, without checking caching, PHP workers and renewal price first.
Frequently asked questions
Does WordPress need a plugin for HTTP/3?
No. WordPress does not set the HTTP version. Your web server or CDN offers HTTP/2 or HTTP/3, and the browser picks the best version both sides support. A plugin cannot add HTTP/3 to a server that lacks QUIC support, so check with your host or CDN first.
Will HTTP/3 improve my Google rankings?
Not on its own. Google does not rank sites by HTTP version alone. HTTP/3 can help page speed on lossy mobile networks, and speed can affect user experience, but caching, image size, server response time and content quality matter more. Treat HTTP/3 as one small part of speed work.
What happens if a visitor's network blocks HTTP/3?
The browser falls back to HTTP/2 or HTTP/1.1. HTTP/3 is offered through an Alt-Svc header or DNS record, and the browser tries it only when it can reach the QUIC endpoint. If UDP is blocked, the visitor still loads the site over TCP. Enabling HTTP/3 does not cut off those visitors.
Do I need a new SSL certificate for HTTP/3?
No new certificate type is needed, but you do need a valid HTTPS certificate. HTTP/3 only works over HTTPS in browsers, and Cloudflare requires an SSL certificate at its edge. LiteSpeed also requires HTTPS with a trusted certificate. A free certificate from a trusted issuer is enough.
Is HTTP/2 still safe to use in November 2026?
Yes. HTTP/2 is widely supported, still carries most web traffic on large networks, and remains a sound choice when HTTP/3 is not offered. In 2025 Cloudflare saw half of its requests on HTTP/2. Keep your server and TLS setup current, and use HTTP/2 without worry.
Why does my site show h2 even after I enabled HTTP/3?
The browser may need a first load over HTTP/2 to learn that HTTP/3 exists, so reload the page and check again. UDP port 443 may also be blocked, the CDN may apply HTTP/3 only to the visitor leg, or that page may take a different path. Check the Alt-Svc header and test more than one page.
Sources
- RFC 9114: HTTP/3 IETF
- Evolution of HTTP MDN Web Docs
- HTTP/3 (with QUIC) Cloudflare
- QUIC and HTTP/3 Support LiteSpeed Documentation
- HTTP | 2024 | The Web Almanac by HTTP Archive HTTP Archive
- The 2025 Cloudflare Radar Year in Review Cloudflare
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.
