Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/cdn
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.
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Can you do a code review on our web app's route and asset loading behavior? Please point out specific files or requests that introduce extra network or layout overhead, and specify the measurement technique you would use to verify the issue.
| Checked | Without skill | With skill |
|---|---|---|
| Evaluates whether static assets are served from a content delivery network or edge distribution | Missed | Passed |
| Checks CDN caching headers or asset caching configuration | Missed | Passed |
The instructions your model reads when the skill loads.
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/rules/performance/cdn
test cases passed, vs 21 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.