“HTTP/2 Push allows websites to save loading time by skipping network round-trips. Because it reduces the effects of latency so well, it may become a viable alternative to CDNs for websites with moderate traffic. But in order to save resources when doing HTTP/2 Push, a web server should know which as…”— Nejc Vukovic, shimmercat.com
“One major goal is to allow the use of a single connection from browsers to a Web site.”— IETF HTTP Working Group, http2.github.io
“In the future, we plan to develop new tools to help our users to make more educated decisions in regards to Server Push. Over time, CloudFlare will even be able to predict the best assets to push automatically.”— Vlad Krasnov, blog.cloudflare.com
“Generally, the downside of pushing assets that will end up unused is only the wasted bandwidth, while the upside is a speedup equivalent to one round trip from the client to our edge network.”— Vlad Krasnov, blog.cloudflare.com
“Server Push enables websites and APIs to speculatively deliver content to the web browser before the browser sends a request for it. This behavior is opportunistic, since in some cases, the content might already be in the client’s cache or not required at all.”— Vlad Krasnov, blog.cloudflare.com
“This layer allows client and server to disintegrate the HTTP payload into small, independent and manageable interleaved sequence of frames. This information is then reassembled at the other end.”— Ali Raza, kinsta.com