CDN and edge platform · Snapshot 23 October 2026
Sites on Azure Front Door/CDN
282 measured sites rely on Azure Front Door/CDN as their cdn and edge platform. How common it is by popularity band, how its customers configure related checks, and the continuity steps worth taking.
- Sites
- 282
- Median readiness index
- 66/100
- Profiles
- 155
<1% of all measured sites
all sites: 64
top-50K sites
Share by popularity band
| Chrome UX Report band | Share of measured sites | Sites |
|---|---|---|
| Top 1K | <1% | 3 |
| Top 5K | <1% | 7 |
| Top 10K | <1% | 18 |
| Top 50K | <1% | 139 |
| Top 100K | 1% | 55 |
| Top 500K | <1% | 43 |
| Top 1M | <1% | 17 |
Related checks among Azure Front Door/CDN customers
| Check | Lane | Observed | All sites | Measured |
|---|---|---|---|---|
| HTTP/2 negotiated | Accelerate | 98% | 90% | 282 |
| HTTP/3 advertised | Accelerate | 3.6% | 37% | 274 |
| HTML compressed | Accelerate | 83% | 93% | 270 |
| Static files cached for 30 days or more | Accelerate | 45% | 51% | 250 |
| HSTS kept for at least a year | Harden | 63% | 34% | 274 |
| TLS 1.3 negotiated | Harden | 98% | 91% | 282 |
| Modern image formats in use | Accelerate | 46% | 40% | 233 |
Continuity steps for Azure Front Door/CDN customers
- Document how the site would be served if the edge layer misbehaves: which DNS records change to bypass the proxy, what that exposes, and who can make the change.
- Keep the origin's own TLS certificate valid so that a bypass does not break HTTPS.
- Keep edge configuration (redirects, headers, cache and firewall rules) exported or in version control so it can be rebuilt or moved.
- Rehearse serving from the origin during a quiet period, so you know it can carry traffic without the cache.
Status Is UP dependency continuity toolkitWebsite recovery planService guide: Microsoft Azure