The State of Web Vitals

HTML document CDN on React sites

Direct from origin versus Cloudflare, Fastly, CloudFront, or Akamai: how serving the main HTML document through an edge CDN changes Time to First Byte (514 ms on Cloudflare vs 681 ms from origin) and Largest Contentful Paint.

Field data PhoneDesktopAll Scope All sites October 2026 edition · Phone field outcomes · React sites only
React Scoped to 9,570 sites out of 210,902 analyzed (frameworks) Compare with all sites →

47.1% of React sites have no an HTML edge CDN. Of the 52.9% that do, 69% use Fastly as, and 95% of those sites have a good LCP, against 84% of all React sites.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with Fastly as an HTML edge CDN have a good LCP most often: 95%, against 84% of all React sites. Sites with Cloudflare as CDN have it least often, at 81%.

SitesGood, needs improvement, poor LCPMedian
All React sites5,48884%1.4s
Fastly 36.4%1,93695%1.1s
Netlify Edge 0.6%5383%2.2s
Amazon CloudFront 7.2%38682%1.4s
Cloudflare 7.5%43881%1.6s
Vercel Edge 0.1%580%2.0s
Direct from origin (no CDN) 47.1%2,59877%1.6s
Akamai 1.0%7268%1.9s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
2

An HTML edge CDN usage

52.9% of React sites use an HTML edge CDN, and two in three of those use Fastly as.

All React sites 9,570 sites
Direct from origin (no CDN) 47.1% An HTML edge CDN 52.9%
Sites with an HTML edge CDN 5,066 sites
Fastly 68.8% Cloudflare 14.2% Amazon CloudFront 13.6%
Fastly 68.8% Cloudflare 14.2% Amazon CloudFront 13.6% Akamai 2.0% Netlify Edge 1.2% Vercel Edge 0.3%
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
3

Where an HTML CDN saves time: TTFB and the four LCP phases

Across the four LCP sub-parts in Chrome's field data, the largest gap between Fastly as and no sits in time to first byte (TTFB): 406 ms median for Fastly as against 681 ms for no. Overall median field LCP is 1.1s for Fastly as (TTFB 406 ms, load delay 447 ms, load duration 112 ms, render delay 151 ms) versus 1.6s for no.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
All React sites 4,169502 ms433 ms433 mslab 439 ms1.4s
Netlify Edge 441089 ms949 ms96 mslab 106 ms2.3s
Direct from origin (no CDN) 1,921681 ms414 ms414 mslab 421 ms1.6s
Akamai 60841 ms438 ms323 ms438 mslab 407 ms1.9s
Fastly 1,506406 ms447 ms447 mslab 453 ms1.1s
Amazon CloudFront 291477 ms453 ms453 mslab 460 ms1.4s
Cloudflare 345514 ms478 ms478 mslab 473 ms1.6s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
4

An HTML edge CDN per platform

Wix sets the an HTML edge CDN to Fastly as on 58% of its sites, and 94% of Wix sites have a good LCP, against 84% of all sites.

PlatformAn HTML edge CDN on its sitesGood LCP
All React sites 9,570 sitesDirect from origin (no CDN) 47%Fastly 36%84%
Wix 5,824 sitesFastly 58%Direct from origin (no CDN) 27%94%
WordPress 2,342 sitesDirect from origin (no CDN) 82%63%
Direct from origin (no CDN) Fastly Cloudflare Amazon CloudFront Akamai Netlify Edge Vercel Edge
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
5

HTML edge CDN or the platform

Does the platform explain the an HTML edge CDN difference?

On Wix, 96% of sites with Fastly as an HTML edge CDN have a good LCP, against 91% of Wix sites without an HTML edge CDN. Within Wix, sites with Fastly as an HTML edge CDN have a good LCP more often.

Why putting the HTML document on an edge CDN cuts TTFB

Static assets like images and scripts are easy to put on a CDN, but the browser cannot discover any of them until the main HTML document arrives. Routing the main domain through an edge network terminates DNS, TCP, and TLS at a point of presence near the visitor, and full-page HTML caching at the edge removes the origin server round trip entirely. In Chrome's field data, serving HTML through Cloudflare cuts median TTFB to 514 ms and Fastly cuts it to 406 ms, compared with 681 ms for documents served directly from the origin.

The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
6

Understanding HTML document CDN delivery

Serve the main HTML document through an edge CDN and cache anonymous page views at the edge wherever possible. Across the dataset, 47.1% of sites still serve HTML directly from an origin server (77% good LCP, 681 ms median TTFB), while sites on Cloudflare (81% good LCP, 514 ms TTFB) and Fastly (95% good LCP, 406 ms TTFB) start rendering significantly earlier. Even when HTML cannot be cached publicly, edge TLS termination, HTTP/3 support, and tiered origin routing cut connection latency on every navigation.

Go fix it Configure Cloudflare for passing the Core Web Vitals → Time to First Byte → Free website cache warmer →
The State of Web Vitals · October 2026 · React: 9,570 crawled sites · 5,488 with phone field dataBy Arjen Karel · corewebvitals.io/state-of-cwv
Related signals ETag present → Requests via CDN → HTTP protocol mix → HTTP protocol → By Arjen Karel · 9,570 crawled React sites (5,488 with phone Chrome field data, October 2026) · How we measured