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 · 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
185,262 sites
77.0%
Top share
origin
86ms
Top INP
Median for origin

77.0% of HTML documents are served without a CDN.

The State of Web Vitals · Q2 2026 · 189,915 sites · all devices 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
fastly79ms4% of sites
origin86ms77% of sites
akamai87ms3% of sites
cloudflare89ms13% of sites
cloudfront103ms3% of sites
vercel114ms1% of sites
netlify121ms0% of sites
VariantShare of sitesMedian
fastly 6,437 sites
4%
79ms
origin 142,621 sites
77%
86ms
akamai 4,955 sites
3%
87ms
cloudflare 23,785 sites
13%
89ms
cloudfront 6,141 sites
3%
103ms
vercel 980 sites
1%
114ms
netlify 343 sites
0%
121ms

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

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

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

VariantSitesPassing INPINP
Akamai 2.7% 4,955 97% 87ms
Origin 77% 142,621 95% 86ms
Cloudflare 12.8% 23,785 94% 89ms
Fastly 3.5% 6,437 94% 79ms
Cloudfront 3.3% 6,141 91% 103ms
Vercel 0.5% 980 91% 114ms
Netlify 0.2% 343 75% 121ms
Good Needs Improvement Poor Sorted best-passing first · median colored by its own rating · pass = good INP (200ms at p75) · one value per site

97% of Akamai sites pass INP. Netlify trails 22 points behind. computed

The State of Web Vitals · Q2 2026 · 189,915 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 Netlify, 78% do.

The split is bigger on INP. With Akamai, 97% of sites pass it. With Netlify, 75% 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