Performance · NinjaOps Guides

Edge Caching: The 3-Header Setup for Static Sites

Edge caching means a user in Tokyo gets your page from Tokyo, not Virginia. It's the single highest-leverage speed fix for content sites — three headers and a purge strategy.

How to fix it

  1. Send Cache-Control with s-maxage so the edge will store the asset.
  2. Send a Vary only where needed (every Vary cuts your hit rate).
  3. Purge on deploy: version your content, keep the edge fresh, keep it warm.
  4. Verify with the cf-cache-status header: HIT means you did it.

Diagnose this exact issue on your site — free

The 100-Point Affiliate Site Grader runs this check (and 40+ more) on your live site in ~10 seconds. No signup.

Want it fixed for you?

The Zero-Overhead Affiliate Playbook walks through every gap in this guide in 14 days on a $0 stack. Join the launch list →

More Performance fixes: