thedaviddias/Front-End-Checklist / skills/cdn
cdn
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
| references/rule.md | markdown | 5.1 KB |
references/rule.md
View on GitHub# Use a content delivery network
> Static assets are served from a CDN for reduced latency and faster delivery.
**Priority:** high · **Difficulty:** intermediate · **Time:** 30 min
---
CDNs distribute your content across global edge servers for faster delivery.
## Code Example
```javascript
// next.config.js - assets automatically served via CDN
module.exports = {
// Enable image optimization via CDN
images: {
domains: ['images.example.com'],
},
// Configure headers for CDN caching
async headers() {
return [
{
source: '/static/:path*',
headers: [
{
key: 'Cache-Control',
value: 'public, max-age=31536000, immutable',
},
],
},
]
},
}
```
## Why It Matters
A CDN serves static assets from geographically distributed servers—users download from the nearest location, dramatically reducing latency and improving load times.
## CDN Benefits
| Benefit | Impact |
|---------|--------|
| Reduced latency | 50-70% faster for distant users |
| Traffic handling | Auto-scales for traffic spikes |
| DDoS protection | Edge network absorbs attacks |
| SSL/TLS offloading | Edge handles encryption |
| Caching | Reduces origin server load |
## Common CDN Providers
| Provider | Best For | Key Features |
|----------|----------|--------------|
| Cloudflare | General purpose | Free tier, WAF, Workers |
| Vercel | Next.js/React apps | Edge functions, instant cache invalidation |
| AWS CloudFront | AWS ecosystem | Lambda@Edge, S3 integration |
| Fastly | Real-time updates | Instant purging, VCL |
| Akamai | Enterprise | Global reach, advanced security |
## Cloudflare Configuration
```javascript
// DNS setup points to Cloudflare, which proxies to origin
// Page rules for caching
// *.example.com/static/* -> Cache Level: Cache Everything, Edge TTL: 1 month
// Workers for custom logic
addEventListener('fetch', event => {
event.respondWith(handleRequest(event.request))
})
async function handleRequest(request) {
const url = new URL(request.url)
// Serve static assets from cache
if (url.pathname.startsWith('/static/')) {
const response = await fetch(request)
const headers = new Headers(response.headers)
headers.set('Cache-Control', 'public, max-age=31536000')
return new Response(response.body, { ...response, headers })
}
return fetch(request)
}
```
## AWS CloudFront Setup
```yaml
# CloudFormation template
AWSTemplateFormatVersion: '2010-09-09'
Resources:
Distribution:
Type: AWS::CloudFront::Distribution
Properties:
DistributionConfig:
Origins:
- DomainName: !GetAtt S3Bucket.DomainName
Id: S3Origin
S3OriginConfig:
OriginAccessIdentity: ''
DefaultCacheBehavior:
TargetOriginId: S3Origin
ViewerProtocolPolicy: redirect-to-https
CachePolicyId: 658327ea-f89d-4fab-a63d-7e88639e58f6 # CachingOptimized
Compress: true
PriceClass: PriceClass_100 # US, Canada, Europe
Enabled: true
```
## React App with CDN Assets
```tsx
// Use CDN URLs for static assets
const CDN_URL = process.env.NEXT_PUBLIC_CDN_URL || ''
function ImageWithCDN({ src, alt, ...props }: ImageProps) {
// Prepend CDN URL to relative paths
const cdnSrc = src.startsWith('http') ? src : `${CDN_URL}${src}`
return <img src={cdnSrc} alt={alt} {...props} />
}
// Environment variables
// .env.production
// NEXT_PUBLIC_CDN_URL=https://cdn.example.com
```
## Cache Headers for Different Asset Types
```nginx
# Nginx configuration for origin server
location /static/ {
# Immutable assets (hashed filenames)
add_header Cache-Control "public, max-age=31536000, immutable";
}
location /assets/ {
# Assets that may change
add_header Cache-Control "public, max-age=86400, stale-while-revalidate=604800";
}
location / {
# HTML pages - short cache with revalidation
add_header Cache-Control "public, max-age=0, must-revalidate";
}
```
## Measuring CDN Performance
```javascript
// Check if resources are served from CDN
function checkCDNHeaders() {
const resources = performance.getEntriesByType('resource')
resources.forEach(resource => {
// CDN typically adds specific headers
// Check in Network tab: cf-ray (Cloudflare), x-amz-cf-id (CloudFront)
console.log(resource.name, {
transferSize: resource.transferSize,
encodedBodySize: resource.encodedBodySize,
duration: resource.duration
})
})
}
// Test from multiple locations using tools like:
// - WebPageTest (select test locations)
// - Pingdom (global testing)
// - GTmetrix (performance comparison)
```
## Standards
- Use web.dev: Learn Performance as the standard for measuring the final production behavior, not just local synthetic output.
- Use Chrome Developers: Lighthouse overview as the standard for measuring the final production behavior, not just local synthetic output.
## Verification
### Automated Checks
- Check response headers for CDN indicators (cf-ray, x-cache)
- Run Lighthouse from different regions
### Manual Checks
- Test from multiple geographic locations
- Verify cache hit rate in CDN dashboard
- Compare latency with and without CDNRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |