On 7 November 2017, we announced HTTP/2 on all our hosting plans. The improvement allows browsers and servers to exchange a page’s resources more efficiently.
To use it on your site, you need HTTPS with a valid certificate and a compatible browser. We handle server configuration.
What changes with HTTP/2?
A page is not just one file. In addition to its main document, it usually needs images, stylesheets, scripts and other resources. HTTP/2 exchanges multiple requests and responses simultaneously over one TCP connection.
This capability is called multiplexing. Each exchange uses its own stream, and its data can be interleaved with other resources, avoiding reliance on multiple connections for parallel transfers.
HTTP/2 also compresses headers, the control information accompanying requests and responses. This reduces repeated information during browsing.
What it adds to your website
The main benefit is making better use of the connection between browser and server. A page with many resources can reduce some of the waiting time associated with downloading them.
For anyone running a business website, store or blog, this improvement comes from the infrastructure: it does not require replacing the design or migrating the application. You do not need to install a plugin to activate the server protocol either.
Overall speed still depends on image size, scripts, caching and how long the application takes to generate a page. HTTP/2 improves transport; optimising those components remains worthwhile.
HTTPS and compatibility
Browsers use HTTP/2 over HTTPS connections. Our plans include SSL certificates so you can provide an encrypted connection.
If a page still opens over HTTP, has an invalid certificate or loads insecure resources, its configuration should be checked. A CDN or proxy in front of the site also participates in the visitor’s connection.
Cloudflare’s HTTP/2 documentation explains how the protocol works in that service and the certificate requirement on its network.
How it relates to HTTP/3
HTTP/2 remains useful even with a newer version available. HTTP/3 uses QUIC to improve other aspects of transport, particularly when packets are lost.
Browsers and servers negotiate a compatible protocol. If you need to check HTTPS or your domain’s connection, contact our team. We will help review what your site uses and what can be improved.