Cache and Response Header Baseline Configuration
Key takeawayCaching decides how fast returning visitors load the site, and response headers decide how browsers treat the content. Both are low-level settings whose failures show up as broken styling, updates that never appear and security scan deductions.
Industries and use cases
- After connecting a new server or CDN
- When users still see the old page after a release
- When a security scan flags missing headers
- When static assets are re-downloaded and traffic looks abnormal
Checklist
| Check item | Pass criteria | Risk level | Fix hint |
|---|---|---|---|
| Static asset caching | CSS, JS, fonts and images use long Cache-Control lifetimes of at least 30 days | High | Fingerprinted filenames allow one year; without hashes, shorten to 7 days. |
| HTML caching | HTML responses use no-cache or a short lifetime so updates propagate | High | Long HTML caching leaves visitors on an old version after release. |
| ETag and Last-Modified | At least one validator is configured and 304 responses carry an empty body | Medium | Let the server generate them instead of hard-coding timestamps. |
| Compression | Text assets use gzip or brotli with at least 60% size reduction | High | Enable it at server or CDN level and confirm the encoding header on CSS and JS. |
| HSTS | Strict-Transport-Security is enabled with a max-age of at least six months | Medium | Confirm the whole site and its subdomains support HTTPS before extending the lifetime. |
| Content type | Correct Content-Type is returned: text/html for HTML and application/xml for XML | Medium | Wrong types make browsers render as plain text or trigger a download. |
| Security headers | X-Content-Type-Options, Referrer-Policy and X-Frame-Options are set | Low | Inject them at one entry point rather than maintaining them page by page. |
| CSP policy | Content Security Policy does not block first-party scripts or analytics | Medium | Run in report-only mode for a week before switching to enforcement. |
| Server signature | Responses expose no exact version numbers or internal paths | Low | Disable detailed version information to reduce targeted probing. |
| CDN hit rate | Static asset hit rate above 80% with stable origin traffic | Medium | Review cache keys so meaningless parameters do not fragment the cache. |
| Redirect caching | 301 responses may be cached while 302 responses are not given long lifetimes | Medium | Permanent redirects reduce requests, while temporary ones must stay reversible. |
| Post-release purge | The release process includes purging HTML and CDN caches | High | Write the purge step into the checklist instead of relying on memory. |
Common misjudgements
- Setting long cache lifetimes on everything: without hashed filenames, visitors never receive the new version.
- Treating a 304 response as proof of correct caching, when it only shows validation works, not that the lifetime is sensible.
- Enabling compression without verifying it, since some servers compress only certain types and the header reveals the truth.
How to use this checklist
- Pair with the image and mobile sheets, as caching is the last step of performance work.
- Check immediately after changing server or CDN and review headers quarterly.
- Link with the release review sheet so cache purging is fixed inside the release process.
FAQ
What cache lifetime is appropriate?
A year for hashed static assets, and no caching or a few minutes for HTML.
Is server caching still needed with a CDN?
Yes. Two layers together balance hit rate and update speed.
Can caching cause indexing problems?
Rarely, but long HTML caching can serve stale content to crawlers, so set it carefully.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.
If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.
Related checklists
Product Page Review Before a B2B Site Goes LiveImage Assets: Alt Text, Naming and Compression ReviewBreadcrumbList Configuration ReviewLanding Page Content Consistency ReviewMobile Usability Baseline ChecksNote: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.