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
CloudFlare figured out how to make the Web one second faster — CloudFlare customers can tap into the protocol to shave loading times off their domains.
Context & Ripple Effects
Server Push is the payoff of an adoption arc CloudFlare has been running for months: after Chrome dropped SPDY in favor of HTTP/2, the company pushed the new protocol out network-wide in December with its HTTP/2 rollout to all users, and today it is switching on the protocol's headline performance feature on top of that base.
The move also slots into Google's broader speed campaign — last fall Google partnered with CloudFlare, Fastly, Level 3 and Highwinds to accelerate delivery of Google Cloud content, making CDN operators the delivery mechanism for its performance agenda. With AMP later showing how much load time matters to publishers, CloudFlare turning Server Push into a customer-facing toggle keeps it central to that push.
First-order effects
- CloudFlare customers can immediately enable Server Push on their domains, with the company targeting up to a 15% reduction in page and app load times across its network within a year.
Second-order effects
- Rival CDNs named in Google's own acceleration partnership — Fastly, Level 3 and Highwinds — face pressure to match Server Push as a standard feature or cede the performance argument to CloudFlare.
Third-order effects
- If the pattern holds, web-performance tuning migrates from developer-side optimization to edge-network defaults — the same trajectory CloudFlare followed when it later made TLS 1.3 and automatic HTTPS rewrites default for all clients — leaving AMP-style page-level fixes as the complement rather than the primary lever for speed.
The trend: CDN providers are absorbing web-performance optimization into their platforms as a default service tier, with browser-driven protocol transitions like HTTP/2 setting the pace.