HTTP/3 and QUIC: what changes

What is HTTP/3 and why should you care?

If your website loads slowly or users have a poor experience on mobile networks, the problem probably isn't your code; it stems from the underlying HTTP/2 protocol. HTTP/3 is a new version of the HTTP protocol that uses QUIC (Quick UDP Internet Connections) instead of TCP. This fundamental change solves problems that have plagued developers and site administrators for years.

In this article, we'll examine in technical but understandable language exactly what problems HTTP/3 solves, how much real impact it has on website speed, and how you can enable it on your server.

The HTTP/2 problems that HTTP/3 solves

HTTP/2 was introduced in 2015 and promised greater speed. But in practice, it has two fundamental problems that manifest themselves in real-world networks.

1. Head-of-Line Blocking at the TCP level

HTTP/2 supports Multiplexing, meaning multiple requests are sent simultaneously over a single TCP connection. However, TCP itself guarantees that packets arrive in order. If a packet is lost, all subsequent packets that have already arrived at the destination wait in the buffer until the lost packet is retransmitted. This phenomenon is called Head-of-Line Blocking.

Imagine 10 images are loading from a server. If the packet for the third image is lost, images 4 through 10, which arrived intact, cannot be rendered until the lost packet is retransmitted and received. On networks with packet loss above 1% (common on Wi-Fi and mobile networks), this problem becomes highly noticeable.

2. High cost of establishing a connection

Every HTTPS connection requires a full handshake. With HTTP/2 and TLS 1.3, this process takes at least one Round-Trip Time (RTT). On mobile networks where RTT can be 100 milliseconds, this delay is noticeable. Additionally, if the connection is interrupted (for example, when a user switches from Wi-Fi to 4G), the entire process must start over.

How does QUIC solve these problems?

QUIC is a new transport protocol built on UDP that implements all the features of TCP (such as reliable delivery and congestion control) along with TLS 1.3 in an integrated manner. This design offers several advantages.

1. Eliminating Head-of-Line Blocking

In QUIC, each stream is independent. If a packet in stream number 3 is lost, only that stream is paused, and other streams continue without delay. This means in the image example above, images 4 through 10 render immediately, and only image 3 is displayed with a delay.

2. Faster handshake

QUIC natively includes TLS 1.3, and its handshake typically completes in one RTT. For repeat connections (for example, a user who visits your site daily), QUIC supports 0-RTT, meaning the request is sent with the first packet, and there is no delay in establishing the connection.

3. Stable connections with Connection Migration

One of QUIC's unique features is Connection Migration. If a user switches from Wi-Fi to a mobile network, the QUIC connection is not interrupted because the connection is identified by a Connection ID rather than an IP address and port. With HTTP/2, this switch means a complete connection drop and a restart of the handshake.

The real impact of HTTP/3 on website speed

The main question is: does HTTP/3 actually make your website faster? The answer depends on your circumstances.

When is the improvement noticeable?

• Mobile users: On 4G and 5G networks, packet loss and IP changes are common. HTTP/3 can reduce loading time by up to 30%.
• Sites with many resources: If your page has more than 50 HTTP requests, multiplexing without blocking has a significant impact.
• International users: If your users access your site from other countries, high RTT makes a faster handshake more important.

When is the difference small?

• Simple sites: If your page has fewer than 10 requests and users are on stable networks, the difference may be less than 5%.
• Powerful servers with CDN: If you use a CDN that keeps content close to the user, RTT is minimized and the handshake advantage diminishes.

As a general rule, HTTP/3 provides a 10 to 30 percent improvement on unstable networks and for heavy sites. Under ideal conditions, the difference may be negligible.

How to enable HTTP/3 on your server

To enable HTTP/3, three conditions must be met: server support, CDN support (if used), and user browser support. Fortunately, all modern browsers (Chrome, Firefox, Safari, Edge) support HTTP/3.

1. Enabling in Nginx

From version 1.25.0 onward, Nginx supports HTTP/3 experimentally. To enable it, you need to compile the ngx_http_v3_module module. In your server directive, add the following settings:

server {
    listen 443 ssl;
    listen 443 quic reuseport;
    listen [::]:443 ssl;
    listen [::]:443 quic reuseport;

    ssl_certificate     /etc/ssl/certs/example.com.crt;
    ssl_certificate_key /etc/ssl/private/example.com.key;
    ssl_protocols       TLSv1.3;

    add_header Alt-Svc 'h3=":443"; ma=86400' always;
    add_header QUIC-Status $quic_status;
}

The Alt-Svc line tells the browser that HTTP/3 is available. The value ma=86400 means this announcement is valid for 24 hours.

2. Enabling in Apache

Apache has experimental HTTP/3 support from version 2.4.54 onward. You need to enable the mod_http3 module:

LoadModule http3_module modules/mod_http3.so
Protocols h2 http/1.1 h3

<VirtualHost *:443>
    ServerName example.com
    Protocols h3 h2 http/1.1
    ProtocolsHonorOrder On
</VirtualHost>

3. Using a CDN

If you use a CDN, HTTP/3 is likely already enabled automatically. Cloudflare and Fastly have had HTTP/3 enabled since 2020. In this case, your users benefit from HTTP/3 even if your origin server only supports HTTP/2, because the connection between the user and the CDN uses QUIC.

Common errors and troubleshooting tips

When setting up HTTP/3, you may encounter the following issues:

1. UDP port is closed

HTTP/3 works over UDP, not TCP. If your firewall hasn't opened UDP port 443, the QUIC connection won't be established, and the browser will silently fall back to HTTP/2. This fallback happens silently, and you may not realize HTTP/3 isn't working.

To check, use the following command:

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

If the response includes the alt-svc: h3=":443" header, it means the server has announced HTTP/3. To confirm the connection is established, use curl -v --http3 and look for the line Using HTTP/3.

2. OpenSSL version mismatch

QUIC requires TLS 1.3. If your server's OpenSSL version is 1.1.1 or lower, you cannot enable HTTP/3. Check your OpenSSL version with the openssl version command and upgrade if necessary.

3. Conflict with HTTP/2 settings

Some HTTP/2 settings, such as http2_push in Nginx, are not compatible with HTTP/3. If you use Server Push, it's better to disable it, as HTTP/3 and modern browsers are moving toward using 103 Early Hints.

The impact of HTTP/3 on SEO and user experience

Google has stated that loading speed is one of the ranking factors in search results. HTTP/3 indirectly affects SEO because:

• Reduced bounce rate: If your site loads faster for mobile users, the likelihood of users returning to search results decreases.
• Improved Core Web Vitals: Metrics like LCP (Largest Contentful Paint) and INP (Interaction to Next Paint) improve with reduced latency.
• More stable user experience: No connection drops when switching networks provides a better experience for users on the move.

The future of HTTP/3 and summary

According to W3Techs statistics, more than 30% of websites worldwide supported HTTP/3 in 2024, and this number is growing rapidly. If your site hasn't enabled HTTP/3 yet, now is a good time to take action.

To get started, follow these steps:

1. Check your web server version and upgrade if necessary.
2. Open UDP port 443 in your firewall.
3. Apply HTTP/3 settings according to your web server's documentation.
4. Test functionality with curl --http3.
5. If you use a CDN, make sure HTTP/3 is enabled in your CDN settings.

Finally, remember that HTTP/3 is not a magic solution; rather, it's a tool that has a significant impact under specific conditions. If your site is already optimized in terms of code and infrastructure, HTTP/3 can be the final piece of the puzzle for achieving optimal speed. ServerNet also provides the ability to use modern web protocols in its hosting and cloud server services, ensuring your website is always one step ahead.