At a glance the headline numbers for CDN performance
Performance breakdown by cdn.
The ranking sorted by TTFB at p75, fastest first
| # | CDN | TTFB p75 | Passing | Sites |
|---|
No data above the minimum sample threshold this edition.
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.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.