HTTP/2, explained
The older HTTP/1.1 handled requests over a few connections, so files could wait in line. HTTP/2 uses multiplexing, where many requests share a single connection at the same time.
It also compresses headers, which cuts repeated data. Browsers only use HTTP/2 over encrypted HTTPS connections, so you need an SSL certificate.
This changed some old advice. Merging everything into one giant file matters less now, although too many small files can still hurt.
Most modern hosts and CDNs support it already, and many also offer HTTP/3, which runs over a different transport called QUIC. To check a site, open your browser's network panel and look at the protocol column.



