Set cache-control headers with long TTL and hashed filenames.
- Set cache-control headers with long TTL and hashed filenames1 cited source1 category
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Proper caching improves repeat load speed by leveraging browser and CDN caches effectively.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- Audit response headers for static resources using browser devtools or webpagetest.
- Implement cache-control with max-age set to weeks or months for immutable assets.
- Use hashed filenames or query strings for cache busting on updates.
- Verify that HTML responses do not have overly long caching to allow content updates.
- Test repeated page loads for reduced network and improved speed.
Watch for
Short or missing cache TTLs cause unnecessary re-downloads, hurting performance under repeat visits.
Definition of done
Static assets have cache-control headers with long TTL and use hashed filenames to allow caching without stale content.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.