QUIC
ProtocolsQUIC is a transport protocol developed to improve web performance and reliability by running over UDP and integrating encryption by default. It reduces connection setup time, supports multiplexing without head-of-line blocking across streams, and enables connection migration when a client changes networks. QUIC is the foundation for HTTP/3, helping sites load faster, especially on mobile and high-latency links.
How It Works
QUIC replaces many functions traditionally handled by TCP plus TLS with a single protocol carried over UDP. A client begins with a cryptographic handshake that establishes keys and validates the server, then immediately sends application data once the session is ready. Because encryption is built in, QUIC avoids the separate TLS negotiation step that can add extra round trips in older stacks. When a client has previously connected, QUIC can resume sessions with fewer exchanges, reducing time to first byte.
Unlike HTTP/2 over TCP, QUIC multiplexes multiple independent streams inside one connection without suffering TCP head-of-line blocking, where one lost packet can stall all streams. QUIC also supports connection migration: if a user switches from Wi-Fi to cellular, the connection can continue using a new network path without restarting from scratch. Congestion control and loss recovery are handled within QUIC, and servers typically enable it at the edge (load balancer, reverse proxy, or CDN) or directly in the web server stack to speak HTTP/3.
Why It Matters for Web Hosting
For hosting buyers, QUIC matters because it is closely tied to HTTP/3 support and real-world page speed, especially for visitors on mobile networks, high-latency routes, or lossy connections. When comparing plans, check whether the host supports HTTP/3/QUIC at the server, reverse proxy, or CDN layer, and whether UDP traffic on port 443 is allowed. Also consider operational fit: QUIC can shift some performance and observability tooling compared with TCP-based setups.
Common Use Cases
- Serving websites over HTTP/3 to reduce latency and improve perceived load time
- Improving performance for global audiences where round-trip times are higher
- Enhancing reliability for users on unstable networks (mobile, public Wi-Fi)
- Reducing impact of packet loss on multiplexed resources like images, scripts, and API calls
- Supporting seamless browsing when clients change networks via connection migration
QUIC vs TCP
TCP is a reliable transport protocol that most web traffic has historically used, with encryption added separately via TLS. QUIC provides similar reliability features but runs over UDP and integrates encryption and stream multiplexing at the transport layer. In practice, QUIC can reduce handshake overhead and avoid TCP head-of-line blocking across streams, but it requires HTTP/3-capable software and network paths that permit UDP on port 443, which can affect compatibility and troubleshooting.