The State of Web Vitals

Subresource CDN providers and the Core Web Vitals

Across audited sites, 99.3% (204,824) fetch requests from unfronted origin or custom hosts (86% good LCP), while 44.4% load assets via Cloudflare (85% good LCP), 25.3% via Amazon CloudFront (85% good LCP), and 18.8% via Fastly (86% good LCP, 1.4s median).

Field data PhoneDesktopAll Scope All sites October 2026 edition · Desktop field outcomes

1.2% of sites use Vercel Edge subresource CDN distribution, and 88% of those sites have a good LCP, against 86% of all sites.

The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 206,252 sites with subresource CDN distributionBy Arjen Karel · corewebvitals.io/state-of-cwv
1

LCP pass rate

Sites with Vercel Edge subresource CDN distribution have a good LCP most often: 88%, against 86% of all sites. Sites with Netlify Edge subresource CDNs have it least often, at 80%.

SitesGood, needs improvement, poor LCPMedian
All sites69,74586%1.4s
Vercel Edge Network 1.2%1,04288%1.4s
Fastly CDN 18.8%15,03186%1.4s
Direct origin / custom host 99.3%69,22986%1.4s
Akamai CDN 4.6%5,60386%1.4s
Cloudflare CDN 44.4%37,58385%1.4s
Amazon CloudFront 25.3%22,09185%1.5s
Netlify Edge 0.5%36780%1.6s
GoodNeeds improvementPoorSites: with Chrome field data
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 206,252 sites with subresource CDN distributionBy Arjen Karel · corewebvitals.io/state-of-cwv
2

Subresource CDN distribution usage

Origin/custom hosts is the most used: 99.3% of sites. Vercel Edge is 1.2% of sites.

Sites using each option (sites can use more than one) 206,252 sites
Direct origin / custom host 99.3% Cloudflare CDN 44.4% Amazon CloudFront 25.3%
Direct origin / custom host 99.3% Cloudflare CDN 44.4% Amazon CloudFront 25.3% Fastly CDN 18.8% Akamai CDN 4.6% Vercel Edge Network 1.2% Netlify Edge 0.5%
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 206,252 sites with subresource CDN distributionBy Arjen Karel · corewebvitals.io/state-of-cwv
3

LCP phase breakdown by CDN serving page subresources

Across the four LCP sub-parts in Chrome's field data, the largest gap between Vercel Edge and Netlify Edge sits in time to first byte (TTFB): 296 ms median for Vercel Edge against 518 ms for Netlify Edge. Overall median field LCP is 1.5s for Vercel Edge (TTFB 296 ms, load delay 552 ms, load duration 127 ms, render delay 229 ms) versus 1.6s for Netlify Edge.

Median LCP phase breakdown (Chrome field p75) Load delay Median LCP
Sites with subresource CDN distribution 50,974571 ms274 ms191 ms274 mslab 316 ms1.4s
Direct origin / custom host 50,656572 ms275 ms191 ms275 mslab 316 ms1.4s
Akamai CDN 4,636593 ms281 ms212 ms281 mslab 328 ms1.5s
Cloudflare CDN 28,692588 ms313 ms209 ms313 mslab 358 ms1.5s
Amazon CloudFront 17,359570 ms345 ms213 ms345 mslab 386 ms1.5s
Fastly CDN 11,543522 ms362 ms217 ms362 mslab 398 ms1.5s
Netlify Edge 263518 ms400 ms205 ms400 mslab 411 ms1.6s
Vercel Edge Network 676296 ms552 ms229 ms552 mslab 588 ms1.5s
TTFB Resource load delay Resource load time Element render delay
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 206,252 sites with subresource CDN distributionBy Arjen Karel · corewebvitals.io/state-of-cwv
4

Understanding subresource CDN providers

Which CDN edges actually serve the images, scripts, and fonts on a page

Even when a site's main HTML document is served directly from an origin server, its subresources (images, scripts, fonts, third-party libraries) frequently traverse global CDNs. Across all audited sites, 44.4% (91,586) load subresources from Cloudflare (85% good LCP, 1.4s median), 25.3% (52,129) from Amazon CloudFront (85% good LCP), 18.8% (38,747) from Fastly (86% good LCP, 1.4s median), and 4.6% (9,532) from Akamai (86% good LCP).

Serve static subresources (especially the LCP hero image, critical CSS, and web fonts) from the same edge CDN fronting your HTML document so requests coalesce over a single HTTP/2 or HTTP/3 connection. Across all audited sites, 44.4% fetch subresources from Cloudflare (85% good LCP) and 18.8% from Fastly (86% good LCP).

Go fix it Configure Cloudflare for passing the Core Web Vitals → Time to First Byte →
The State of Web Vitals · October 2026 · 210,902 crawled sites · 69,745 with desktop field data · 206,252 sites with subresource CDN distributionBy Arjen Karel · corewebvitals.io/state-of-cwv
Platform & Framework Takeaways

How subresource CDN distribution plays out per platform

What the field data shows when you isolate a single CMS or framework.

WordPress 65,509 sites
42.1% / 19.2% Cloudflare / CloudFront subresources on WordPress

99.8% of WordPress sites fetch subresources from origin/custom hosts, 42.1% use Cloudflare, and 19.2% use CloudFront.

Across 65,509 WordPress sites, 99.8% serve subresources from origin or custom hosts (76% good LCP), 42.1% use Cloudflare (74% good LCP), 19.2% use CloudFront (72%), and 10.5% use Fastly (74%).

Read the WordPress subresource CDN breakdown →
React & Next.js 9,570 sites
85% / 82% good LCP (Fastly / CloudFront on React)

74.5% of React & Next.js sites load subresources from CloudFront (82% good LCP) and 68.0% from Fastly (85%).

Across 9,570 React sites, 74.5% load subresources from Amazon CloudFront (82% good LCP, 1.4s median), 68.0% from Fastly (85% good LCP, 1.3s median), and 37.2% from Cloudflare (75% good LCP).

Related signals Last-Modified present → Uncompressed text responses → Cacheable responses → HTML size (kB) → By Arjen Karel · 210,902 crawled sites (69,745 with desktop Chrome field data, 206,252 sites with subresource CDN distribution, October 2026) · How we measured