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 · Desktop 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
48ms
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 · desktop 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
origin48ms77% of sites
fastly48ms4% of sites
akamai49ms3% of sites
cloudflare53ms13% of sites
cloudfront60ms3% of sites
vercel68ms1% of sites
netlify77ms0% of sites
VariantShare of sitesMedian
origin 142,621 sites
77%
48ms
fastly 6,437 sites
4%
48ms
akamai 4,955 sites
3%
49ms
cloudflare 23,785 sites
13%
53ms
cloudfront 6,141 sites
3%
60ms
vercel 980 sites
1%
68ms
netlify 343 sites
0%
77ms

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

The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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 99% 49ms
Origin 77% 142,621 99% 48ms
Cloudflare 12.8% 23,785 99% 53ms
Vercel 0.5% 980 99% 68ms
Fastly 3.5% 6,437 98% 48ms
Cloudfront 3.3% 6,141 97% 60ms
Netlify 0.2% 343 90% 77ms
Good Needs Improvement Poor Sorted best-passing first · median colored by its own rating · pass = good INP (200ms at p75) · one value per site

99% of Akamai sites pass INP. Netlify trails 9 points behind. computed

The State of Web Vitals · Q2 2026 · 189,915 sites · desktop 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 Vercel, 90% of sites pass the LCP. With Netlify, 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 189,915 sites, representing millions of real page loads · How we measured