The State of Web Vitals

Main CDN

Which CDN, if any, serves the HTML document itself.

Field data PhoneDesktopAll Scope All sites Q2 2026 edition · Phone field outcomes
Metric LCP INP CLS
1

At a glance the headline numbers for Main CDN

Which CDN, if any, serves the HTML document itself.

7
Categories
185,477 sites
77.0%
Top share
origin
1.6s
Top LCP
Median for origin

77.0% of HTML documents are served without a CDN.

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
2

Main CDN who uses what, and how fast each group loads

Median LCP
0
0.5s
1s
1.5s
2s
2.5s
3s
3.5s
4s
fastly1.4s3% of sites
cloudflare1.5s13% of sites
origin1.6s77% of sites
akamai1.6s3% of sites
cloudfront1.7s3% of sites
vercel1.8s1% of sites
netlify2.1s0% of sites
VariantShare of sitesMedian
fastly 6,447 sites
3%
1.4s
cloudflare 23,815 sites
13%
1.5s
origin 142,788 sites
77%
1.6s
akamai 4,958 sites
3%
1.6s
cloudfront 6,145 sites
3%
1.7s
vercel 981 sites
1%
1.8s
netlify 343 sites
0%
2.1s

Fastly sites post the best median LCP (1.4s). Netlify sites trail at 2.1s. Correlation, not causation. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
3

Passing LCP per main CDN which group passes the LCP most often

VariantSitesPassing LCPLCP
Cloudflare 12.8% 23,815 85% 1.5s
Fastly 3.5% 6,447 84% 1.4s
Akamai 2.7% 4,958 81% 1.6s
Origin 77% 142,788 81% 1.6s
Vercel 0.5% 981 79% 1.8s
Cloudfront 3.3% 6,145 79% 1.7s
Netlify 0.2% 343 74% 2.1s
Good Needs Improvement Poor Sorted best-passing first · median colored by its own rating · pass = good LCP (2.5s at p75) · one value per site

85% of Cloudflare sites pass LCP. Netlify trails 11 points behind, leaving 26% of its sites failing. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · phone field datacorewebvitals.io/state-of-cwv
4

Why this matters for the Core Web Vitals, and where to start fixing it

Everything starts after the HTML arrives. The document's TTFB sits under every other phase: the browser cannot discover, download or render anything before it has the markup. Serving the document through a CDN terminates TLS close to the visitor, and when the HTML is edge-cached it removes the origin round trip completely.

HTML is the hardest thing to put on a CDN because it is the dynamic part. Full-page edge caching is the big win when the content allows it. Even without it, edge termination and a warm route to the origin cut the TTFB.

How does this affect the Core Web Vitals?

Main CDN correlates with the LCP. With Cloudflare, 85% of sites pass the LCP. With Netlify, 74% do.

Go fix it Configure Cloudflare for passing the Core Web Vitals → Time to First Byte → Free website cache warmer →
Related signals ETag present → Requests via CDN → HTTP protocol mix → HTTP protocol → Chrome field data from 189,915 sites, representing millions of real page loads · How we measured