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 · 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
94,906 sites
76.4%
Top share
origin
96ms
Top INP
Median for origin

76.4% of HTML documents are served without a CDN.

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

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

Median INP
0
100ms
200ms
300ms
400ms
500ms
fastly89ms4% of sites
origin96ms76% of sites
akamai103ms3% of sites
cloudflare104ms13% of sites
cloudfront118ms3% of sites
vercel132ms1% of sites
netlify140ms0% of sites
VariantShare of sitesMedian
fastly 3,357 sites
4%
89ms
origin 72,501 sites
76%
96ms
akamai 2,663 sites
3%
103ms
cloudflare 12,431 sites
13%
104ms
cloudfront 3,241 sites
3%
118ms
vercel 538 sites
1%
132ms
netlify 175 sites
0%
140ms

Little daylight between the groups: every variant sits near 89ms median INP. computed

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

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

VariantSitesPassing INPINP
Akamai 2.8% 2,663 95% 103ms
Origin 76.4% 72,501 92% 96ms
Fastly 3.5% 3,357 91% 89ms
Cloudflare 13.1% 12,431 91% 104ms
Cloudfront 3.4% 3,241 87% 118ms
Vercel 0.6% 538 85% 132ms
Netlify 0.2% 175 70% 140ms
Good Needs Improvement Poor Sorted best-passing first · median colored by its own rating · pass = good INP (200ms at p75) · one value per site

95% of Akamai sites pass INP. Netlify trails 25 points behind, leaving 30% of its sites failing. computed

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

The split is bigger on CLS. With Origin, 90% of sites pass it. With Cloudfront, 79% 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