Web & Development

HTTP/3 in 2026: How QUIC Works, When It Improves Performance, and How to Enable It

HTTP/3 in 2026: How QUIC Works, When It Improves Performance, and How to Enable It

Learn how HTTP/3 and QUIC differ from HTTP/2, when they improve website performance, and how to enable and verify HTTP/3 with Cloudflare, NGINX, curl, and browser developer tools.

HTTP/3 is a standardized web protocol supported by major browsers, content delivery networks and modern server software. But is it faster than HTTP/2? Does it improve Core Web Vitals? And how can a website owner verify that it actually works?

HTTP/3 changes the transport layer used to deliver web content. It can reduce connection overhead and improve performance on networks experiencing packet loss. It cannot compensate for inefficient JavaScript, oversized images or slow application code.

This guide explains the protocol, its practical advantages and limitations, and how to enable and test it safely.

What is HTTP/3?

HTTP/3 is the third major version of the Hypertext Transfer Protocol. It preserves familiar HTTP requests, responses, methods, status codes and URLs.

The major difference is transport. HTTP/1.1 and HTTP/2 typically run over TCP, while HTTP/3 uses QUIC over UDP. QUIC provides reliable delivery, multiplexed streams, connection management and integrated TLS 1.3 security.

HTTP/3 was standardized in RFC 9114, with the underlying QUIC transport described in RFC 9000.

HTTP/1.1 vs HTTP/2 vs HTTP/3

Feature HTTP/1.1 HTTP/2 HTTP/3
Transport TCP TCP QUIC over UDP
Multiplexed HTTP streams No, not within one connection Yes Yes
Secure transport TLS typically used for HTTPS TLS typically used for HTTPS TLS 1.3 integrated with QUIC
Transport head-of-line blocking across streams Not applicable in the same way Yes Avoided between independent QUIC streams
Connection migration Not inherent to TCP Not inherent to TCP Supported by QUIC

HTTP/2 multiplexes multiple requests on one TCP connection, but TCP presents an ordered byte stream. When a TCP segment is lost, data arriving after it cannot be delivered to the application in order until the missing bytes are recovered. This can delay several independent HTTP/2 streams.

QUIC tracks ordering independently for each stream. Loss affecting one stream need not prevent the delivery of already received data on another. Packet loss still requires recovery and congestion control still matters; HTTP/3 does not make unreliable networks magically reliable.

Why QUIC can connect faster

TCP establishes its transport connection before completing the TLS handshake. QUIC combines transport and cryptographic negotiation, potentially reducing the round trips required to establish a secure connection.

The benefit depends on network latency and connection reuse. It can be more noticeable on mobile networks or long-distance connections than on a fast local connection.

QUIC also supports session resumption and optional 0-RTT early data, but HTTP/3 does not automatically mean 0-RTT is enabled.

Does HTTP/3 actually improve website performance?

It can, especially on lossy or high-latency networks and for pages transferring multiple resources concurrently. On a stable, low-latency connection, HTTP/2 may already perform very well.

HTTP/3 can potentially help loading metrics such as Largest Contentful Paint (LCP) when network delays contribute materially to loading time. It does not directly fix slow JavaScript event handlers responsible for poor Interaction to Next Paint (INP), nor does it inherently prevent Cumulative Layout Shift (CLS).

There is no guarantee that enabling HTTP/3 improves a Lighthouse score or search rankings. Measure actual user experience before and after the change.

How browsers discover HTTP/3

Browsers can learn about an HTTP/3 endpoint through the Alt-Svc response header:

Alt-Svc: h3=":443"; ma=86400

This advertises HTTP/3 on port 443, with an alternative-service freshness lifetime of 86,400 seconds. Clients may initially use HTTP/2 and then try HTTP/3 on a later connection. DNS HTTPS records are another discovery mechanism.

Advertising HTTP/3 does not prove that it works. The server or CDN must accept QUIC traffic at the advertised endpoint.

Option 1: Enable HTTP/3 with Cloudflare

For websites already proxied through Cloudflare, the simplest option may be enabling HTTP/3 at the edge. Check Cloudflare's current dashboard instructions under its speed and protocol optimization settings.

Cloudflare documents support for HTTP/3 on its plans, subject to the relevant zone and certificate requirements.

Important: HTTP/3 between the browser and Cloudflare does not mean the connection from Cloudflare to your origin also uses HTTP/3. A Joomla or WordPress origin can continue serving HTTP/2 or HTTP/1.1 while visitors use HTTP/3 to the CDN.

See Cloudflare's HTTP/3 documentation.

Option 2: Enable HTTP/3 directly in NGINX

NGINX supports HTTP/3 through the ngx_http_v3_module, introduced in NGINX 1.25.0. Check your actual installed build; a version number alone does not prove that the module is compiled in.

Illustration of the article's main concept
nginx -V 2>&1

Look for --with-http_v3_module. Consult the documentation for the installed version and TLS/QUIC implementation.

A simplified configuration for a compatible recent build might include:

server {
    listen 443 ssl;
    listen 443 quic reuseport;

    server_name example.com;
    http2 on;

    ssl_certificate /etc/nginx/certs/fullchain.pem;
    ssl_certificate_key /etc/nginx/certs/privkey.pem;
    ssl_protocols TLSv1.2 TLSv1.3;

    add_header Alt-Svc 'h3=":443"; ma=86400' always;

    root /var/www/example.com/public;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

This is an illustration, not a complete production configuration. Adapt certificate paths, routing, security directives and the web root. For WordPress or Joomla, preserve the existing PHP-FPM and rewrite rules instead of replacing them with the static example.

NGINX's HTTP/3 module has been described as experimental in official documentation, so confirm its current status and test carefully before production deployment.

Open UDP port 443

Normal HTTPS typically uses TCP port 443; QUIC uses UDP port 443. A firewall or load balancer that allows TCP but blocks UDP can prevent HTTP/3 from working even when ordinary HTTPS succeeds.

Check host firewall rules, cloud security groups, hosting provider configuration and upstream proxies.

Validate the NGINX configuration before reloading:

sudo nginx -t

If the configuration is invalid, do not reload production services.

Official reference: NGINX HTTP/3 module.

Test HTTP/3 with curl

HTTP/3 support depends on how curl was built. First inspect its features:

curl --version

To require HTTP/3 without fallback:

curl --http3-only -I https://example.com/

To attempt HTTP/3 while allowing fallback:

curl --http3 -I https://example.com/

The second command may succeed using HTTP/2 or HTTP/1.1, so success alone is not proof of HTTP/3.

Print the negotiated version:

curl --http3 -o /dev/null -s -w '%{http_version}\n' https://example.com/

An output of 3 indicates HTTP/3 was used for that request. See curl's HTTP/3 documentation.

Test HTTP/3 in the browser

Open browser developer tools, select the Network panel and enable the Protocol column. Depending on the browser, negotiated protocols may appear as h3, h2 or http/1.1.

You can also inspect navigation timing:

Technical workflow illustration
const navigation = performance.getEntriesByType('navigation')[0];
console.log(navigation?.nextHopProtocol);

For resource requests:

for (const resource of performance.getEntriesByType('resource')) {
    console.log(resource.name, resource.nextHopProtocol);
}

Cross-origin resource timing restrictions can hide some details. With a CDN, the browser generally reports the browser-facing connection rather than the CDN-to-origin protocol.

What about 0-RTT security?

QUIC's optional 0-RTT feature allows certain data to be sent early during resumed connections, potentially reducing latency.

However, early data can be replayed. Applications must not assume that replay-sensitive actions are safe to process without safeguards.

Operations such as payments, account changes and other state-changing requests require particular care. GET requests should not unexpectedly change state. Enabling HTTP/3 does not require enabling 0-RTT.

Treat 0-RTT as a separate security decision.

Common HTTP/3 problems

The browser still uses HTTP/2

Check that HTTP/3 is correctly advertised, UDP port 443 is reachable, the server build supports QUIC and the browser has had an opportunity to discover the alternative service.

HTTP/3 works on one network but fails on another

Some corporate networks, VPNs or firewalls restrict UDP traffic. Keep HTTP/2 available for clients that cannot connect using QUIC.

HTTP/3 works through a CDN but not at the origin

That can be normal. The CDN may terminate HTTP/3 and connect to the origin using another HTTP version.

HTTP/3 is enabled but performance is unchanged

Investigate slow database queries, uncached pages, large assets, JavaScript execution and rendering work. Transport is only one part of overall performance.

Should WordPress and Joomla websites enable HTTP/3?

HTTP/3 is principally a server or CDN capability, not a CMS content feature. Joomla and WordPress generally do not need different PHP application code to serve content over HTTP/3.

If a mature CDN or hosting platform already supports it, enabling and testing HTTP/3 may be worthwhile.

If the change requires replacing a stable server stack or taking on experimental maintenance, weigh the operational risk against the expected performance benefit.

Do not prioritize HTTP/3 over obvious bottlenecks such as slow PHP, poor caching, excessive JavaScript or oversized images.

How to measure the benefit

Compare HTTP/2 and HTTP/3 under similar conditions, including network latency, packet loss, cache state, content and server region.

Measure connection establishment, time to first byte, resource loading and real-user page performance. Segment results by device and network conditions where possible.

One synthetic test on a powerful desktop is not sufficient evidence that the change benefits visitors.

Conclusion

HTTP/3 is a meaningful evolution of web transport. QUIC reduces transport-level head-of-line blocking across independent streams, supports efficient secure connection establishment and can improve reliability on challenging networks.

Its advantages are not universal. HTTP/2 remains useful, and a reliable fallback is essential.

Enable HTTP/3 because it improves a measurable part of your infrastructure, not because a newer protocol number automatically means a faster website.

Official references