Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when auditing slow page loads, heavy assets, or rendering delays related to Use a content delivery network. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-20 | ✓→✓ | = Same ✓ | 3% | 0% |
| case-13 | ✓→✓ | = Same ✓ | 5% | 0% |
| case-19 | ✓→✓ | = Same ✓ | -2% | 0% |
| case-02 | ✓→✓ | = Same ✓ | -10% | 0% |
A CDN serves static assets from geographically distributed servers—users download from the nearest location, dramatically reducing latency and improving load times.
Check if static assets are served from a CDN and if the CDN is properly configured.
Configure a CDN to serve static assets with proper caching headers and geographic distribution.
Explain how CDNs reduce latency by serving content from geographically distributed servers.
Review the routes, assets, and loading behavior that affect Use a content delivery network. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/performance/cdn
Other measured skills in the registry, with their headline benchmark lift.