Cache-Control header missing or unfavorable
Clean caching rules reduce loading time and server load.
Clean caching rules reduce loading time and server load performance errors should be prioritized according to affected templates and user view. Not every technical warning is equally business critical.
Set caching by content type instead of flat-rate
A product image and a personal account view require different cache rules. A missing cache control header on an immutable font file gives away reuse; however, the same message on a private response may give rise to explicitly specifying its protection.
Example: Recognizing the Result
Illustrative example: A versioned font file is transferred again each time a page changes, while a personal account view accidentally gets the same public cache rule.
# Beispiel für eine versionierte, öffentlich identische Datei
Cache-Control: public, max-age=31536000, immutable
# Beispiel für eine nicht zu speichernde persönliche Antwort
Cache-Control: no-storeLimit cause and implement correction
Targeted limitation of the cause
Group the affected responses by HTML, static files, and personalized data. Read the headers of a normal GET retrieval and check in the browser whether a second request is cached or validated at the server. Also consider age headers and rules of the upstream CDN.
Change and follow-up audit
Provide versioned, publicly identical files with a suitable long life span. For changing HTML, use a deliberate update strategy. Private data must not accidentally end up in a common cache. no-cache requires re-validation; no-store prohibits storage.
After the next deployment, check that new file versions are loaded immediately and that old URLs continue to deliver the corresponding content. A high performance score does not justify caching user accounts or individually generated reports.
What makes you recognize a suitable correction
The font may be reused; for private answers, browser and shared caches must be treated according to the need for protection. After a deployment, test the new asset URL.
Classification and boundaries
When is this indication not a clear error?
The right lifetime depends on changeability and personalization. no-cache means re-validation, not a fundamental storage ban.
Further documentation
Cache-Control header missing or unfavorable according to CMS and cause
Many audit messages can be resolved faster if they are grouped by system, page type and technical cause. CMS indentations are only linked where the cache control header is missing or unfavorably has a clearly own cause or fixed route in the respective system.
For this error, there is currently no own CMS deepening, because the correction is usually not sufficiently system-specific. Take advantage of the general causes and checks on this page.
Frequent causes of this error
Related SEO Errors
Appropriate Seitenreport checks
This error should not be checked in isolation. The following tools and clusters help to narrow down the cause faster and to cleanly prioritize the affected URL groups.