---
title: "HTTP/3 WordPress Guide: What QUIC Changes for Your Site"
description: "HTTP/3 and WordPress: what QUIC really changes (connections, mobile, head-of-line blocking), which servers support it and how to check your site."
url: https://hosterwise.com/en/blog/wordpress-http3-quic/
language: en
updated: 2026-10-15
source: Hosterwise
translations:
  fr: https://hosterwise.com/blog/http3-quic-wordpress.md
---

Canonical page: <https://hosterwise.com/en/blog/wordpress-http3-quic/>

[Performance](https://hosterwise.com/en/category/performance-en/) 9 min read

# HTTP/3 and QUIC: What They Change for Your WordPress Site

HTTP/3 and WordPress: what QUIC really changes (connections, mobile, head-of-line blocking), which servers support it and how to check your site.

By The Hosterwise team · Hosterwise technical and support team

Published November 19, 2026

## In this article

Share

- [Share on LinkedIn (new tab)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fwordpress-http3-quic%2F)
- [Share on X (new tab)](https://x.com/intent/post?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fwordpress-http3-quic%2F&text=HTTP%2F3%20and%20QUIC%3A%20What%20They%20Change%20for%20Your%20WordPress%20Site)
- [Send by e-mail](mailto:?subject=HTTP%2F3%20and%20QUIC%3A%20What%20They%20Change%20for%20Your%20WordPress%20Site&body=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fwordpress-http3-quic%2F)

[HTTP/3](https://hosterwise.com/en/glossary/#http3) is the third major version of the web’s core protocol. It swaps TCP for [QUIC](https://hosterwise.com/en/glossary/#quic), an encrypted transport running over UDP: connections open faster, a lost packet no longer stalls every file in flight, and a connection survives a switch from Wi-Fi to mobile data. For a WordPress site, the gains show up mostly on mobile and patchy networks; HTTP/3 doesn’t replace caching or page optimisation, and it is handled entirely on the server side.

*Article current as of 19 November 2026. References: IETF RFCs and the [LiteSpeed](https://hosterwise.com/en/glossary/#litespeed), Nginx and curl documentation.*

**Key takeaways**

- **HTTP/3** (RFC 9114, June 2022) runs on **QUIC** (RFC 9000, May 2021), which has **[TLS 1.3](https://hosterwise.com/en/glossary/#ssl-tls)** built in: there is no unencrypted HTTP/3.
- Three real-world gains: **faster connection setup**, **no more TCP head-of-line blocking**, and **connection migration** when the visitor’s network changes.
- What it doesn’t change: **how long PHP takes to build a page** and the **weight** of images and scripts. [Page caching](https://hosterwise.com/en/glossary/#page-cache) still comes first.
- Modern browsers support it; on the server side, **LiteSpeed** supports it natively, **Nginx**’s module is still labelled experimental, and **Apache** doesn’t document it.
- Nothing to configure in WordPress: you need a compatible server, a **valid certificate** and **UDP port 443 open**.

## What are HTTP/3 and QUIC?

HTTP/3 is the version of HTTP that runs over QUIC instead of TCP. QUIC, standardised by the IETF in 2021, handles reliability, stream multiplexing and TLS 1.3 encryption itself, on top of UDP. HTTP/3, standardised in 2022, keeps HTTP’s semantics (methods, headers, status codes), so your pages, URLs and WordPress itself stay exactly the same.

The reference documents come from the IETF: [RFC 9000](https://www.rfc-editor.org/rfc/rfc9000.html) defines QUIC, [RFC 9114](https://www.rfc-editor.org/rfc/rfc9114.html) defines HTTP/3, and RFC 9204 defines QPACK, the header compression designed for QUIC (replacing [HTTP/2](https://hosterwise.com/en/glossary/#http2)’s HPACK).

| | HTTP/1.1 | HTTP/2 | HTTP/3 |
| --- | --- | --- | --- |
| — | — | — | — |
| Transport | TCP | TCP | QUIC over UDP |
| Parallel requests on one connection | No (one at a time) | Yes, multiplexed | Yes, multiplexed and independent |
| Encryption | Optional (TLS) | Required in practice by browsers | Always, TLS 1.3 built in |
| Opening a new connection | TCP, then TLS | TCP, then TLS | Combined transport and crypto handshake |
| A lost packet blocks… | The current request | Every request on the connection | Only the affected stream |
| Visitor changes network | New connection | New connection | Connection kept (migration) |
| Header compression | None | HPACK | QPACK |

*Summary based on IETF RFCs 9000, 9001, 9114 and 9204.*

## What does HTTP/3 actually change for a WordPress site?

HTTP/3 mainly speeds up delivery: fewer round trips to open a connection, no site-wide stall when a packet goes missing, and connections that survive network changes. Visitors on mobile data or crowded Wi-Fi benefit the most. A page that is slow to generate, however, stays slow.

### 1. Faster connection setup

With HTTP/2, the browser first opens a TCP connection, then negotiates TLS. QUIC combines both. For returning visitors, QUIC can even send data in the very first packet (“0-RTT”). That saved time counts towards the TTFB of the first request, and therefore towards LCP: it’s the first link in the chain described in our guide to [WordPress Core Web Vitals](https://hosterwise.com/en/blog/wordpress-core-web-vitals/).

### 2. No more head-of-line blocking

HTTP/2 carries every file of a page (CSS, scripts, images) over a single TCP connection. TCP delivers data in order, so if one packet is lost, everything behind it waits for the retransmission, even unrelated files. RFC 9114 describes this head-of-line blocking problem. With QUIC each stream is independent: a lost image packet doesn’t hold up your CSS.

### 3. Connection migration

A TCP connection is tied to the visitor’s IP address. When a phone moves from Wi-Fi to 4G, it breaks and has to be reopened. QUIC identifies the connection with its own ID, which survives the address change, so a shopper browsing your store on the way out of the house doesn’t start from scratch.

### What HTTP/3 doesn’t change

The protocol doesn’t speed up PHP or the database. If WordPress takes a second to build a page, HTTP/3 won’t show it sooner; only a page cache can. A 2 MB image is still a 2 MB image. Google’s [Optimize TTFB](https://web.dev/articles/optimize-ttfb) guide makes the same point: HTTP/3 solves TCP’s head-of-line blocking, but response time depends first on the server, caching and redirects. If your TTFB is high, start there with our guide to [reducing WordPress TTFB](https://hosterwise.com/en/blog/reduce-wordpress-ttfb/).

## How does a browser find out a site speaks HTTP/3?

Usually the browser connects over HTTP/2 first, and the server advertises HTTP/3 on UDP port 443 through the `Alt-Svc` response header. Later requests then switch to HTTP/3. An HTTPS-type DNS record can also advertise HTTP/3 before the very first visit.

A compatible server sends a header like this:

```
alt-svc: h3=":443"; ma=86400
```

`h3` means HTTP/3, `:443` is the port and `ma` is how long, in seconds, the browser may remember it; without `ma`, it defaults to 24 hours, as the [MDN reference for Alt-Svc](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Alt-Svc) explains. If the visitor’s network blocks UDP (some corporate networks do), the browser simply falls back to HTTP/2 over TCP and the site stays reachable.

The HTTPS DNS record (RFC 9460) tells the browser which protocols are available before it even connects (for example `alpn=h2,h3`). It is mostly handled automatically by CDNs and some DNS providers.

## Which web servers support HTTP/3?

LiteSpeed Web Server supports HTTP/3 natively and enables it by default. Nginx has offered an HTTP/3 module since version 1.25.0, still labelled experimental in its documentation and not built by default. The Apache httpd 2.4 documentation doesn’t mention HTTP/3, so Apache sites rely on a CDN or proxy for it.

| Server or service | HTTP/3 | Worth knowing |
| --- | --- | --- |
| — | — | — |
| LiteSpeed Web Server | Native, on by default | HTTP/3 v1 since LSWS 6.0 (2021), QUIC v2 since 6.2; needs a trusted certificate and UDP 443 open |
| Nginx | `ngx_http_v3_module` since 1.25.0 (May 2023) | Labelled experimental in the official docs; must be compiled in |
| Apache httpd 2.4 | Not documented | Use a compatible CDN or proxy in front of the server |
| CDN (Cloudflare, QUIC.cloud…) | Yes, towards visitors | Between the CDN and your server, the protocol depends on the CDN and the origin |

*Status as of 19 November 2026, from each project’s official documentation. Our [LiteSpeed vs Nginx vs Apache comparison](https://hosterwise.com/en/blog/litespeed-vs-nginx-vs-apache-wordpress/) covers the choice of web server in depth.*

How widespread is it? The HTTP chapter of HTTP Archive’s [2024 Web Almanac](https://almanac.httparchive.org/en/2024/http) measured HTTP/3 on 7% of desktop home pages and 9% of mobile ones, while noting that this underestimates it: the crawler arrives with no history, so it never benefits from the `Alt-Svc` advertisement. The author puts real-world support closer to 30%, with most HTTP/3 traffic coming from CDNs.

With a CDN in front of your site, the CDN is what speaks HTTP/3 to your visitors. LiteSpeed notes that its own QUIC support won’t work behind a front-end proxy such as Cloudflare. Conversely, QUIC.cloud paired with a LiteSpeed server gives you HTTP/3 end to end: see our guide to [QUIC.cloud, LiteSpeed’s CDN](https://hosterwise.com/en/blog/quic-cloud-cdn-explained/).

Read also

- [Speed Up WordPress: 15 Practical Actions That Work](https://hosterwise.com/en/blog/speed-up-wordpress/)
- [Best WordPress Hosting 2026: Our Ranking of 7 Hosts](https://hosterwise.com/en/blog/best-wordpress-hosting/)

## How do you check your WordPress site uses HTTP/3?

Open your site in Chrome, go to DevTools, Network tab, and add the Protocol column: `h3` means HTTP/3, `h2` HTTP/2. Reload once, because the very first request often goes over HTTP/2. From the command line on your own computer (no server access needed), curl can force HTTP/3 if it was built with support for it.

```
# 1. Does the server advertise HTTP/3?
curl -sI https://www.example.com/ | grep -i alt-svc

# 2. Can your curl speak HTTP/3? "HTTP3" must appear in the Features line
curl --version

# 3. Force HTTP/3 with no fallback (fails if QUIC can't connect)
curl -sI --http3-only https://www.example.com/

# 4. Print the version used (3 = HTTP/3, with automatic fallback)
curl -s -o /dev/null -w '%{http_version}\n' --http3 https://www.example.com/
```

The curl bundled with some systems, macOS included, isn’t built with HTTP/3, in which case check 1 and the browser tools are the simplest route. Online testers can also check a domain from outside.

If HTTP/3 doesn’t show up, check in this order:

- Does the server or CDN support HTTP/3, and is it switched on?
- Is the SSL certificate valid and trusted (not self-signed)?
- Does the server firewall allow UDP on port 443, not just TCP?
- Is a proxy or CDN in front of the server hiding the `Alt-Svc` header?
- Does the network you’re testing from block UDP (corporate network, VPN)?

## Do you need to configure anything in WordPress?

No. HTTP/3 is negotiated between browser and server, below WordPress: no plugin is needed and none can enable it in the server’s place. The site simply has to be served over HTTPS with a valid certificate. It’s also a good moment to drop a few habits inherited from HTTP/1.1.

- **No need to combine all CSS and JavaScript into one file**: with HTTP/2 and HTTP/3, several small files travel in parallel over one connection, and changing one file doesn’t invalidate the whole cache. Minify, but leave combining off unless measurements say otherwise (the setting we recommend in our [LiteSpeed Cache setup guide](https://hosterwise.com/en/blog/litespeed-cache-setup/)).
- **No need to spread files across subdomains** (domain sharding): every extra domain means another connection.
- **Forget HTTP/2 Server Push**: Chrome disabled it in 2022. To flag a critical resource, use `<link rel="preload">` or the `fetchpriority` attribute.
- **Host fonts and scripts on your own domain** where you can: each third-party domain costs a connection, even over HTTP/3.

## Is HTTP/3 more secure?

HTTP/3 requires TLS 1.3, so no older version can be negotiated, and QUIC authenticates its headers and encrypts most of what it exchanges, including its control information. The 0-RTT mode, which sends a request in the very first packet, can however be replayed by an attacker, so the HTTP/3 standard requires servers to apply replay protections, such as refusing early data for sensitive requests.

For a WordPress site, there’s nothing to do: the server applies these rules. The usual security basics (updates, strong passwords, backups) don’t change.

## HTTP/3 at Hosterwise

At [Hosterwise](https://hosterwise.com/en/), HTTP/3 and QUIC are enabled by default on every plan, on LiteSpeed Enterprise servers with LSCache and free SSL certificates: your visitors benefit with zero configuration, and cached pages are served without running PHP. If the `alt-svc` header doesn’t show up on your site, our 24/7 support team will check the setup with you. Explore our [LiteSpeed WordPress hosting](https://hosterwise.com/en/litespeed-hosting/) or the full list of [included hosting features](https://hosterwise.com/en/wordpress-hosting-features/).

## HTTP/3 and WordPress FAQ

### Does HTTP/3 improve SEO?

Not directly: Google doesn’t rank sites by protocol. HTTP/3 can, however, cut connection setup time and improve the mobile experience, which feeds into Core Web Vitals, one signal among many.

### Do all browsers support HTTP/3?

Recent versions of Chrome, Edge, Firefox and Safari do. A browser without support, or a network blocking UDP, simply uses HTTP/2, so the site stays available to everyone with no special setup.

### Do I need a WordPress plugin to enable HTTP/3?

No. HTTP/3 depends on the web server or CDN, not on WordPress, and no plugin can turn it on. Ask your host whether its servers support it, or look for the `alt-svc` header in your site’s responses.

### Why do browser tools show h2 when my server supports HTTP/3?

On the first connection, the browser doesn’t yet know the server accepts HTTP/3: it learns it from the `Alt-Svc` header and uses it for later requests. Reload the page. If `h2` persists, check the firewall (UDP 443) and the network you’re testing from.

### Does HTTP/3 replace HTTP/2?

No, they coexist. A compatible server offers both and the browser picks. HTTP/2 remains essential as the fallback when UDP is blocked, so there is nothing to switch off.

### Does my WordPress site need a CDN to get HTTP/3?

Not if your host runs a compatible server such as LiteSpeed. You need a CDN for HTTP/3 if your server doesn’t support it (Apache, for instance), or if a CDN is useful for other reasons, such as an international audience.

Share

- [Share on LinkedIn (new tab)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fwordpress-http3-quic%2F)
- [Share on X (new tab)](https://x.com/intent/post?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fwordpress-http3-quic%2F&text=HTTP%2F3%20and%20QUIC%3A%20What%20They%20Change%20for%20Your%20WordPress%20Site)
- [Send by e-mail](mailto:?subject=HTTP%2F3%20and%20QUIC%3A%20What%20They%20Change%20for%20Your%20WordPress%20Site&body=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fwordpress-http3-quic%2F)

## Your WordPress site on a LiteSpeed server

LSCache, HTTP/3, free SSL and 24/7 support: Hosterwise hosting starts at €7.99/month, with free migration.

[Discover LiteSpeed hosting](https://hosterwise.com/en/litespeed-hosting/)

About the author

## [The Hosterwise team](https://hosterwise.com/en/about-us/)

Hosterwise technical and support team

Written and reviewed by the Hosterwise technical team, who run LiteSpeed servers with CyberPanel every day and help customers migrate, secure and speed up their WordPress sites.

## Keep reading

[All articles](https://hosterwise.com/en/blog/)

[Performance](https://hosterwise.com/en/category/performance-en/)

### [QUIC.cloud Explained: LiteSpeed’s CDN for WordPress](https://hosterwise.com/en/blog/quic-cloud-cdn-explained/)

QUIC.cloud CDN explained: WordPress page caching, image optimisation, the new November 2026 plans and step-by-step setup with LiteSpeed Cache.

November 3, 2026 11 min read

[Performance](https://hosterwise.com/en/category/performance-en/)

### [How to Reduce WordPress TTFB: Causes and Fixes](https://hosterwise.com/en/blog/reduce-wordpress-ttfb/)

High WordPress TTFB? Measure it with curl, find the cause (caching, PHP, database, plugins, network) and fix it step by step, with WP-CLI commands.

October 27, 2026 13 min read

[Performance](https://hosterwise.com/en/category/performance-en/)

### [LiteSpeed vs Nginx vs Apache: Which Web Server for WordPress?](https://hosterwise.com/en/blog/litespeed-vs-nginx-vs-apache-wordpress/)

LiteSpeed vs Nginx vs Apache for WordPress: architecture, .htaccess, caching, HTTP/3 and market share compared, plus which one to pick for your site.

October 13, 2026 11 min read

---

Markdown version of <https://hosterwise.com/en/blog/wordpress-http3-quic/>, generated by Hosterwise. Site index for AI assistants: <https://hosterwise.com/en/llms.txt>
