HTTP/3 and QUIC: the new protocol making the internet faster
If you have ever wondered why a page takes a while to load even though you have plenty of fiber, the answer lies in something deeper than bandwidth: in the protocol that carries every byte. For more than two decades, that transport was called HTTP/2 and TCP. Today, the web is migrating to HTTP/3 and to its foundation, QUIC. And it is the kind of change you notice.
The first key to understanding it is to separate two layers we had always taken for granted. HTTP is the “language” your browser and the server speak: requests, responses, headers, cookies. TCP is the “truck” that guarantees packets arrive in order and without losses. For years they worked well together, but TCP has a structural problem: each connection is an individual conversation, and opening a new one is expensive.
That cost is called the handshake. When you visit a secure website, your browser and the server have to agree on encryption. With TCP plus TLS (Transport Layer Security, the protocol that encrypts the connection), that was two complete round trips before sending a single useful byte. On networks with high latency, such as mobile or satellite, that initial delay is very noticeable.
QUIC changes the rules of the game on three fronts. First, it eliminates the double handshake: it combines the transport greeting and the encryption one into a single step, so the first connection can send data almost immediately and the following ones directly without waiting. Second, QUIC travels over UDP (User Datagram Protocol, the fast but “no guarantees” protocol) instead of TCP, and builds on top of it all the reliability TCP gave, but with much less overhead. Third, and perhaps most importantly, it is a multiplexed protocol.
What does multiplexing mean? In HTTP/2, several requests shared a single TCP connection, but with a flaw known as head-of-line blocking: if a packet was lost, everything behind it got stuck waiting for it, even unrelated images or data. QUIC solves this by giving each data stream its own channel within the same connection. If a video loses a packet, the loss only affects that stream; the text and images of the page keep flowing.
Another practical advantage is the 0-RTT connection (zero round-trip time). When you revisit a website you have been to before, your browser keeps a session key and can send data in the first packet, without waiting to greet. That turns reloads and repeated browsing into almost instant experiences.
QUIC also survives network changes better. If you switch from Wi-Fi to mobile data, your IP address changes; with TCP, the connection breaks and has to be rebuilt. QUIC includes a connection identifier that does not depend on the IP, so traffic continues without interruption. It is an almost invisible improvement, but essential in a world of people who never stop moving.
Who is already using it? The big services adopted it long ago: Google Chrome pushed it since 2021, and today most modern browsers, including Firefox and Safari, support it. Platforms like YouTube, Facebook or Cloudflare serve a huge part of their traffic with HTTP/3. The infrastructure itself has been adapting, because QUIC uses UDP and old firewalls tended to block that protocol.
It is not a revolution you see with your eyes: the page keeps loading just as well or better. But under the hood, every load of a modern site is saving milliseconds, resisting packet loss better and handling the growing mobile traffic with elegance. The web has always been a race against latency, and HTTP/3 is the smartest answer we have had so far.
The next time a website loads instantly on your phone, maybe you are witnessing, without knowing it, the latest major modernization of the protocol that sustains the internet.
