What Is QUIC, and Why Do Websites Use It?
A website can use the same broadband connection while changing how its data reaches your browser. QUIC is part of that change, especially when a connection is starting up, losing packets or moving between networks.
The Transport Behind HTTP/3
QUIC is a transport protocol that carries data between devices and servers. Websites use it through HTTP/3 to establish secure connections efficiently and keep separate streams of data moving. It runs over UDP and integrates TLS encryption.
A web page arrives in pieces: the main document, styles, images and scripts. The browser needs a way to request those pieces and receive them correctly. HTTP describes the web requests and responses; the transport underneath handles how the data travels between the two ends.
That distinction matters. HTTP/3 uses QUIC, but QUIC and HTTP/3 are not interchangeable names. QUIC can carry other application protocols too. It is also separate from the browser engine that turns a page’s code into what you see on screen.
HTTPS With HTTP/2
HTTP/2 streams share a TCP connection.
HTTPS With HTTP/3
HTTP/3 uses QUIC streams.
Simplified HTTPS stacks. Both use IP underneath. QUIC supplies reliability and congestion handling above UDP rather than relying on TCP.
UDP alone does not give an application the same delivery guarantees as TCP. QUIC adds its own acknowledgements, loss recovery and flow control. For HTTP/3, that means a website can still deliver a complete file correctly; using UDP does not mean missing parts are simply ignored.
Google developed an earlier version of QUIC, and the IETF standardised the modern transport. The standard treats QUIC as a name, not an acronym, so the old expansion “Quick UDP Internet Connections” does not define today’s protocol.
Why Websites Use QUIC
QUIC changes connection setup, delivery ordering and how a connection can respond to a network change. Those are useful improvements for websites serving lots of small resources across varied connections.
Less Initial Waiting
QUIC combines the transport and cryptographic handshake instead of opening TCP first and then securing it. This can reduce setup delay for a new secure connection.
Streams Can Progress Separately
Lost data on one stream need not hold up delivery on another. The difference becomes useful when several resources are travelling at once.
A Connection Can Survive a Move
Connection IDs can let QUIC maintain a connection when a device’s network address changes, such as during a move from Wi-Fi to mobile data.
Setup delay is part of internet latency. Its effect can be noticeable when a page needs a new connection to a distant server. If a usable connection is already open, there may be much less setup work to save.
On an eligible return connection, QUIC can also use 0-RTT early data. That allows some application data to be sent before waiting for a fresh handshake round trip. It is optional and has replay risks that applications must account for. It does not mean the reply arrives instantly.
Network migration is also a capability, not a promise that every Wi-Fi-to-mobile handover will be seamless. Support, policy and the availability of a working network path still matter.
A Lost Packet Does Not Have to Stop Every Stream
The clearest difference appears when some data goes missing while several streams are active. HTTP/2 can carry many requests together, but TCP still delivers their combined bytes in order.
What Happens After a Lost Packet?
HTTP/2 Over TCP
A gap in the shared TCP byte stream holds up later delivery.
HTTP/3 Over QUIC
Each stream has its own delivery ordering.
Illustrated example: the lost packet carries data only for the HTML stream, and later data for the other streams has arrived. The page may still need the missing HTML before it can finish rendering.
The TCP delay is called transport head-of-line blocking. QUIC avoids that shared ordering dependency between streams. If a lost QUIC packet contains data for several streams, however, those streams can all be affected.
QUIC still responds to congestion, and a page can have dependencies between its resources. A missing stylesheet or script may hold up useful work even when other bytes have arrived. Our packet loss and high ping comparison explains why loss and delay are different problems.
Connection Speed Still Matters
QUIC does not increase the Mbps included in a broadband plan. Large images, server delays, device processing and a congested connection can still dominate the loading time.
A Fast Speed Test Is Only Part of It
A test of sustained throughput does not tell you everything about loading a page made from many requests. Our guide to a fast speed test with slow browsing covers that wider distinction.
How to Tell Whether a Website Is Using It
You can check the protocol used for a web request in Chrome’s developer tools. The useful label is h3, which identifies HTTP/3.
- Open Developer Tools
Open Chrome’s menu, choose More tools, then Developer tools. Select the Network panel.
- Show the Protocol Column
Right-click a heading in the request table and enable Protocol if it is not already visible.
- Reload the Page
Leave the Network panel open and reload. Read the Protocol entry beside each recorded network request.
h3h2http/1.1One page can contact several servers for images, scripts or other resources, so a mixture of protocols is normal. Check a request that actually went over the network rather than assuming a cached entry proves a new QUIC connection was made.
A browser engine name such as Blink is a different label. Our guides to Chrome’s browser engine and the engines used by other browsers explain that part of the software.
What If QUIC Is Blocked?
HTTP/3 commonly uses UDP port 443. HTTPS over TCP can use the same port number, but UDP and TCP are separate transports. A network can therefore allow ordinary HTTPS while restricting QUIC.
If a QUIC connection cannot be established, HTTP/3 clients should try a TCP-based version of HTTP. A request using h2 is not, by itself, evidence of a broken connection. Managed networks, proxies and website configuration can affect which version is used.
For everyday browsing, protocol selection is normally handled by the browser and the website. You do not need a different broadband package simply to use QUIC. If browsing is unreliable, measure the connection properly and investigate the actual symptoms before changing experimental browser settings.
QUIC Changes How the Connection Works
Its value comes from efficient setup, separate streams and support for changing network paths. Look for h3 to identify HTTP/3, and judge the browsing experience alongside the server, device and connection conditions.
QUIC FAQs
Are QUIC and HTTP/3 the same thing?
No. QUIC is a transport protocol. HTTP/3 defines how HTTP uses that transport. QUIC can also carry application protocols other than HTTP.
Does QUIC use TCP or UDP?
QUIC packets travel over UDP. QUIC adds its own secure connection management, stream delivery and loss recovery rather than relying on TCP.
Is QUIC encrypted?
QUIC integrates TLS 1.3 to protect application data and authenticate the server. It is not a VPN and does not hide every detail about the connection.
Is QUIC always faster than TCP-based HTTPS?
No. The result depends on connection setup, packet loss, network behaviour, server implementation and the page itself. QUIC can reduce particular sources of waiting, but there is no universal speed increase.
Do I need a new router to use QUIC?
Normally no special router is required. The browser and website need compatible support, and the network must allow the relevant UDP traffic. Managed network policies can restrict it.
