What it means
Your home page was sent with no Cache-Control, ETag or Last-Modified header, or some of its
static files are cached for less than an hour or not at all. The result shows the headers for each
response we checked.
Why it matters
This is information. Without caching headers, browsers and CDNs guess, which often means downloading the same files on every visit. Static files with a version or hash in their name can be cached for a year, which makes repeat visits much faster.
How to fix it
- For HTML pages, send
Cache-Control: no-cachewith anETag, so browsers check for changes cheaply. - For versioned static files (
app.3f9a.js), sendCache-Control: public, max-age=31536000, immutable. - For files without a version in their name, use a shorter max-age, such as a day, plus an ETag.
- Most build tools add hashes to file names; turn that on so long caching is safe.
Check it worked
Run the standard files check again. The caching table should show the new headers, and the finding should be gone.