The State of Web Vitals

Main CDN

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

Field data PhoneDesktopAll Scope All sites Q1 2026 edition · All devices 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
94,906 sites
76.4%
Top share
origin
0.00
Top CLS
Median for origin

76.4% of HTML documents are served without a CDN.

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
2

Main CDN who uses what, and how stable each group is

Median CLS
0
0.05
0.10
0.15
0.20
0.25
origin0.0076% of sites
cloudflare0.0013% of sites
fastly0.004% of sites
akamai0.003% of sites
vercel0.001% of sites
netlify0.010% of sites
cloudfront0.023% of sites
VariantShare of sitesMedian
origin 72,501 sites
76%
0.00
cloudflare 12,431 sites
13%
0.00
fastly 3,357 sites
4%
0.00
akamai 2,663 sites
3%
0.00
vercel 538 sites
1%
0.00
netlify 175 sites
0%
0.01
cloudfront 3,241 sites
3%
0.02

Little daylight between the groups: every variant sits near 0.00 median CLS. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices field datacorewebvitals.io/state-of-cwv
3

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

VariantSitesPassing CLSCLS
Fastly 3.5% 3,357 89% 0.00
Origin 76.4% 72,501 88% 0.00
Cloudflare 13.1% 12,431 88% 0.00
Akamai 2.8% 2,663 87% 0.00
Vercel 0.6% 538 84% 0.00
Cloudfront 3.4% 3,241 78% 0.02
Netlify 0.2% 175 71% 0.01
Good Needs Improvement Poor Sorted best-passing first · median colored by its own rating · pass = good CLS (0.1 at p75) · one value per site

89% of Fastly sites pass CLS. Netlify trails 18 points behind, leaving 29% of its sites failing. computed

The State of Web Vitals · Q1 2026 · 94,910 sites · all devices 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, 86% of sites pass the LCP. With Cloudfront, 81% do.

The split is bigger on CLS. With Fastly, 89% of sites pass it. With Cloudfront, 78% 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 94,910 sites, representing millions of real page loads · How we measured