My static assets (images, JS, CSS, fonts) are served from my app server or wherever my platform puts them by default, and I want them served properly: fast, cached, and close to users. First, figure out my current situation: how assets are built, where they're served from, and what cache headers they carry today. If I'm on a platform with a built-in CDN (Vercel, Netlify, Cloudflare Pages), verify it's actually being used for my assets rather than assumed. Then: 1. If I have no CDN: recommend the lowest-friction option for my stack (my platform's built-in offering, or Cloudflare in front of the app) and set it up. 2. Cache headers: static assets with content-hashed filenames should get long-lived immutable caching (a year). HTML should get short or no caching so deploys show up immediately. Verify the actual headers being sent, not just the config intent. 3. Filenames: if my build doesn't fingerprint assets (hash in the filename), set that up or explain why my stack makes it unnecessary. Long cache lifetimes without fingerprinting is how users get stuck on old versions. 4. Compression: verify responses are actually compressed (gzip or brotli) for text assets. When done, show me the verification: response headers for a sample of assets demonstrating CDN hits, correct cache-control values, and compression working.