1.5 Performance & Core Web VitalsLowInferred
No browser caching headers
Without caching headers, returning visitors re-download static assets that have not changed. Sensible cache lifetimes make repeat visits feel instant.
What it is
Static assets re-fetched each visit.
Why it matters
Slower repeat visits.
How to fix it
Set cache-control headers.
How to find it on your site
- Check static asset responses for cache-control headers in DevTools or curl -I.
- Identify assets served with no-cache or no caching at all.
- Set long cache lifetimes on fingerprinted static assets and shorter ones on HTML.
- Verify the headers and that updated assets still bust the cache.
Cross-reference to ranking and citation factors
Caching mostly helps repeat visits rather than first load, so the ranking effect is indirect, but it improves real-world experience.
Impact
Low. Inferred.
Evidence
Caching improves repeat-visit performance. web.dev, Core Web Vitals (Google)