CloudFlare activates HTTP/2 Server Push protocol, expects it will decrease page and app load time by up to 15% across its network within a year
Charlie Osborne / ZDNet :
Context & Ripple Effects
Server Push is the second act of CloudFlare's HTTP/2 campaign: after it rolled out HTTP/2 support to all users last December to spur wider adoption, activating Server Push moves the network from merely speaking the new protocol to using its headline feature — letting servers send assets before the browser asks. The groundwork was laid when Chrome dropped SPDY for HTTP/2, giving the protocol a dominant browser backer.
The move also fits CloudFlare's existing position in Google's content-delivery ecosystem, having joined Fastly, Level 3 and Highwinds in Google's partnership to push cloud content to users faster — so faster edge delivery is now both a protocol play and a competitive one against fellow CDN partners.
First-order effects
- CloudFlare customers get up to 15% faster page and app load times across its network within a year without changing their own code, since the optimization happens at the edge.
Second-order effects
- Rival CDNs named alongside CloudFlare in Google's fast-content partnership — Fastly, Level 3, Highwinds — face pressure to activate Server Push themselves or cede a measurable performance gap on shared customers.
Third-order effects
- If the pattern holds, the CDN edge becomes the standard deployment vehicle for new web protocols — a path that continued three years later when Cloudflare, Chrome and Firefox added support for HTTP/3 — shifting protocol adoption from per-site upgrades to network-wide defaults.
The trend: CDN operators are turning protocol upgrades into network-wide defaults, compressing the lag between a web standard's specification and its mass deployment.