At a glance the headline numbers for CDN performance
Performance breakdown by cdn.
The ranking sorted by TTFB at p75, fastest first
| # | Item | TTFB p75 | Passing | Sites | |
|---|---|---|---|---|---|
| 1 | Vercel | 434ms | 92.5% | 538 | |
| 2 | Netlify | 753ms | 81.6% | 175 | |
| 3 | Cloudflare | 974ms | 68.1% | 12,431 | |
| 4 | CloudFront | 1.0s | 65.6% | 3,241 | |
| 5 | Akamai | 1.0s | 65.0% | 2,663 | |
| 6 | Fastly | 1.0s | 61.6% | 3,357 | |
| 7 | No CDN (origin) | 1.1s | 61.6% | 72,501 |
Passing TTFB per item which group passes the TTFB most often
93% of Vercel sites pass TTFB. Fastly trails 31 points behind, leaving 38% of its sites failing. computed
All five vitals at once the whole category without toggling - cell is the pass rate, small number the p75
One row per item, one column per vital - the cell is the share of sites passing, the small number the p75. No toggling needed to see where the category actually differs.
Vercel leads on TTFB: 93% of its sites pass. Fastly trails at 62%. computed
Why this matters for the Core Web Vitals, and where to start fixing it
A CDN sits between your server and your visitors, serving content from a location near each of them instead of from a single origin. That shortens the trip every request makes, which shows up first in Time to First Byte and then in how quickly the main content can paint. A good CDN also handles caching, compression and modern protocols, so the gains reach well beyond raw distance.
Start by making sure the CDN is actually caching your pages and assets rather than passing everything through to the origin. Turn on compression and HTTP/2 or HTTP/3, set sensible cache headers, and check that your largest image is served from the edge. A CDN that passes every request through to the origin gives you almost none of this.
How does your CDN affect Core Web Vitals?
Among the most-used CDNs, Vercel reaches a good TTFB on 92.5% of sites; No CDN (origin) on 61.6%.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.