Skip to content

HTTP/2 and HTTP/3

Entry #237 / 700 · Chapter 5 · 5.2 Speed, rendering and modern front-ends · Read in Chinese →
In one sentence

Later versions of the protocol that carries pages, adding multiplexing, header compression and a lower connection cost.

Analogy Mental model

Upgrading from a country road to a motorway, then to a train. HTTP/1.1 is one lane, HTTP/2 is several, HTTP/3 stops worrying about lanes.

In practice What you actually do

Turn it on at the CDN and verify with the protocol column in the browser. Multiplexing means many small files can be requested at once, which removes most of the reason to bundle everything into one enormous file.

Where people get burned Pitfalls

Optimisations from the previous era become counterproductive. Domain sharding, sprite sheets and aggressive concatenation now add work rather than saving it.

This entry was written in English from the Chinese original, not machine-translated. Read the Chinese version →