HTTP/2 and HTTP/3 Explained for Website Owners

HTTP is the language browsers and servers use to exchange web pages. Like most technology, it has had upgrades. HTTP/2 and HTTP/3 are newer versions designed to load pages faster. As a site owner, you rarely have to do anything technical, but it helps to understand what they offer and how to make sure you're using them.

The problem with the old way

HTTP/1.1 handled requests in a limited way. Browsers opened several connections to download files and still often waited in line. Sites worked around this by combining files, spreading assets across domains, and other tricks.

HTTP/2

HTTP/2 introduced:

• Multiplexing: many requests and responses share one connection at the same time
• Header compression: less repeated overhead
• Prioritization: browsers can signal which resources matter most

The result is that loading many small files is much less costly than before. Browsers only use HTTP/2 over HTTPS in practice, which is another reason to use it. See SSL and HTTPS.

HTTP/3

HTTP/3 uses a different underlying transport called QUIC, which runs over UDP instead of TCP. Its benefits include:

• Faster connection setup, which helps first visits
• Better handling of packet loss. A lost packet only delays the affected stream, not everything. This matters on unreliable mobile networks
• Connection migration, so moving from Wi-Fi to mobile data can continue smoothly

HTTP/3 is supported by current major browsers and by many hosts and CDNs.

How to check what you use

• Open your browser's developer tools, go to the Network panel, and enable the protocol column. Values like h2 or h3 show which version loaded each file
• Online tools can test whether a domain supports HTTP/2 and HTTP/3
• Ask your host or look in their documentation

How to get them

For most small sites, the answer is simple: choose a host or CDN that supports them. Many modern hosts and CDNs enable HTTP/2 and HTTP/3 by default or with a setting. See what is a CDN and how to choose web hosting. Older shared hosting plans or outdated server setups may lack support. If so, it's worth considering whether a move is overdue.

What changes in how you build

• You no longer need to cram everything into a single giant file purely to reduce the number of requests. Still, avoid shipping unused code. See minify CSS and JavaScript
• Domain sharding (spreading assets over many domains) is no longer helpful, and can even hurt
• Reducing total file size still matters most

It's not a magic fix

Faster protocols can't rescue a page with huge images, heavy scripts, or a slow server. They improve how efficiently files are delivered, not how big they are. Combine them with the basics: compressing images, text compression, caching, and fast server response.

The bottom line

HTTP/2 and HTTP/3 deliver files more efficiently, especially on mobile. Choose a host or CDN that supports them, check it's switched on, and keep your pages lean.