At a glance the headline numbers for Main CDN
Which CDN, if any, serves the HTML document itself.
76.4% of HTML documents are served without a CDN.
Main CDN who uses what, and how stable each group is
Fastly sites post the best median CLS (0.02). Cloudfront sites trail at 0.05. Correlation, not causation. computed
Passing CLS per main CDN which group passes the CLS most often
81% of Vercel sites pass CLS. Netlify trails 9 points behind, leaving 28% of its sites failing. computed
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 Cloudfront, 84% do.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.