What HTTP/2 improves
- Multiplexing — multiple requests and responses share a single connection simultaneously, instead of queuing. This eliminates the head-of-line blocking problem of HTTP/1.1.
- Header compression (HPACK) — request and response headers are compressed, reducing overhead on every request.
- Server push — the server can proactively send resources the browser will need.
- Binary protocol — more efficient to parse than HTTP/1.1’s text format.
Requirements
Browsers only use HTTP/2 over HTTPS, so your site needs a valid SSL certificate. All Stablepoint plans include free SSL certificates, so this is already covered.Checking that your site uses HTTP/2
- Open your site in Chrome or Firefox.
- Open developer tools (F12) and go to the Network tab.
- Right-click the column headers and enable the Protocol column.
- Reload the page — resources served over HTTP/2 show h2 in the protocol column.
Optimization notes
Some old HTTP/1.1 optimization techniques are unnecessary (or counterproductive) with HTTP/2:- Domain sharding (spreading assets across multiple domains) — no longer needed; a single multiplexed connection is more efficient.
- Image sprites and file concatenation — less important; many small files are handled efficiently, and separate files cache more granularly.