Browser and shared TTL
Separate max-age, s-maxage, private, public and no-store behavior.
Analyze browser and shared cache policy, TTL and revalidation signals.
Enter a website URL to start
Website caching and origin control
Cache-Control tells browsers, proxies and CDNs whether a response may be stored, for how long and when it must be revalidated.
Policies should match the content. Fingerprinted static assets suit long immutable caching, while dynamic HTML must account for publishing, authentication and personalization.
Separate max-age, s-maxage, private, public and no-store behavior.
Review ETag, Last-Modified, no-cache and conditional-request foundations.
Find Vary: * and missing shared-cache lifetime.
Missing TTLs cause repeated origin requests; excessive TTLs serve stale content; no-store and Vary: * can prevent edge reuse.
Let reusable responses come directly from browsers and edge nodes.
Find unsuitable TTLs and confirm validators are available.
Explain private, public, max-age and s-maxage independently.
The tool requests one public page and analyzes the final response headers. Results use short caching and are not stored as history.
Normalize the URL and bound redirects, addresses, time and response size.
Read Cache-Control, Expires, Age and directive values.
Determine whether browser and shared caches may store the response.
Explain missing, disabled, TTL and Vary problems.
max-age applies to browser and shared caches; s-maxage overrides the shared-cache TTL.
No. It permits storage but requires revalidation before reuse. no-store forbids storage.
Usually not. Long immutable caching is better for content-hashed static assets.
No business database record is created; only short caching reduces duplicate requests.
Continue with compression, protocols, CDN and origin technology evidence.