2.7.6. HTTP/2 and Server Push

Deprecation of HTTP/2 Server Push

In Chrome 106 and newer versions of other Chromium-based browsers, HTTP/2 Server Push support is disabled by default. This is due to the fact that the technology did not live up to expectations and did not become popular. Details can be found in Chrome Developers Blog.


HTTP / 2 and Server Push work only over HTTPS, therefore, to use them, the site must have SSL certificate installed.

HTTP / 2 and Server Push are supported by default hosting.

You can check protocol support, for example, using the verification service HTTP/2 Test or HTTP2.Pro, either in browser developer tools on the network requests tab.

An example of requests made over the HTTP / 2 protocol:

As part of HTTP / 2, Server Push technology is available, which allows «push» site resources to its visitors, without waiting for their browser to download and parse the HTML document, which can positively affect the loading time and page rendering speed in the browser of each of them. The use of this technology is implemented using a special HTTP header Linkwhich lists the resources you need «pushthrough». The title is added by the site itself, for example, using specialized plugins for a specific CMS. Important conditions are the work of the site on HTTPS and the support of Server Push by the browser used.

You can enable Server Push for each specific site in site settings:

You can check the Server Push operation in browser developer tools on the network requests tab.

Example header Link:

An example of resources loaded using Server Push:

The examples used WordPress with a plugin HTTP/2 Push, Async JavaScript, Defer Render Blocking CSS, HTTP2 server push.