> HTTP2 also uses compression, unlike HTTP1, and so the size of the request is significantly smaller - and thus faster.
Also, an HTTP/1.1 server, when configured properly, will use compression as well.
Also, an HTTP/1.1 server, when configured properly, will use compression as well.
They designed a new compression algorithm called HPACK specifically to compress headers in HTTP2: https://http2.github.io/http2-spec/compression.html
In small HTTP/1.1 requests the headers can be much larger than the content, which is part of the motivation for combining files into one request.
Also, some TCP stacks (or an extension option?) will allow data in the first packet, so you don't have to wait for the handshake. Perhaps this doesn't work if the data doesn't fit in a single packet?
Does http2 also compress headers?