HTTP/3 and QUIC, explained (and why your site feels faster)
Every few years the web gets a new version of HTTP, and HTTP/3 is the biggest change in a while — it threw out TCP. Here is what that means in plain terms, and why your phone notices.
HTTP/3 moves the web onto a new transport called QUIC, built on UDP instead of TCP. The payoff is faster connection setup and no more "one lost packet stalls everything", which is exactly the problem on mobile networks. You don't change your site to get it — your CDN speaks it and falls back gracefully for older clients.
HTTP is the language browsers and servers use to talk. For most of the web's life it ran on TCP, a reliable but old transport with some habits that quietly slow things down. HTTP/3 is the version that finally swapped TCP out — and the result is a web that holds up better when your connection is less than perfect.
The problem with the old way
TCP delivers data in strict order. That sounds sensible until you lose a single packet: everything behind it has to wait, even unrelated data, until that one packet is re-sent. It's called head-of-line blocking, and on a shaky mobile connection it's the reason a page can freeze halfway through loading.
What QUIC changes
QUIC is the new transport under HTTP/3. It's built on UDP and adds back the reliability TCP gave you, but smarter. Two things stand out:
That last one is underrated. With TCP, walking out of your house and dropping from Wi-Fi to cellular usually kills the connection. QUIC can carry it across, because it identifies connections by an ID rather than your exact IP and port.
Do you need to do anything?
Mostly no. HTTP/3 is negotiated automatically: a browser that supports it uses it, and one that doesn't falls back to HTTP/2 without anyone noticing. The practical step is making sure whatever sits in front of your site — your CDN — actually offers it.
The biggest wins show up on mobile and on long-distance connections — exactly the visitors who suffer most under TCP. On a fast wired connection the difference is smaller, which is why testing only on your office network can hide the benefit.
HTTP/3 swaps TCP for QUIC to fix connection setup delays and head-of-line blocking. You don't rewrite anything — you just make sure your edge speaks it. The payoff lands where it matters most: phones, weak signals, and visitors far from your origin.
See how NordicCDN does this for your site:
Mads has worked in IT — mostly hosting — since he was 16. He took an early stake in a SaaS company and helped grow it through to its acquisition by Visma, has built and run data-center networks, and served as CTO of a Danish data center. He started NordicCDN to make fast, secure infrastructure simple to use.
