HTTP/2 and HTTP/3

HTTP/2 multiplexes requests over a single connection; HTTP/3 carries them over QUIC, which tolerates erratic mobile networks far better. Both reduce load latency without touching page code.

In practice

Activation is handled at the server or CDN level — our front-ends serve HTTP/2 natively, HTTP/3 through the CDN layer. Gains are most visible on mobile: better packet-loss tolerance, instant connection resumption. The kind of optimization you enable once and forget, to the benefit of every visit.