What problem does this tool solve?
Estimate how much freshness a stored response has left by subtracting its starting age and time since receipt from the applicable lifetime. Use this to plan when to sample the same representation again.
Ten practical questions answered
How do I estimate the next useful time to retest an event listing?
Record the cache lifetime in seconds, the estimated age when you captured it, and time spent since then. Test the same event URL around the remaining interval and compare its revision marker.
Which value should I use for an edge cache versus a visitor’s browser?
Use the applicable shared-cache lifetime such as s-maxage for the edge calculation. For a private browser cache, use the applicable private-cache lifetime. Document each assumption alongside its result.
Why is a five-minute lifetime almost over when the page first appears?
An intermediary may have stored the response earlier. If it arrives 280 seconds old with a lifetime of 300 seconds, only 20 seconds remain before accounting for additional time.
What happens if my captured age is larger than the lifetime?
The remaining interval becomes zero and the reported age shows how far it has advanced. Check the actual revalidation or stale-serving behavior in the receiving cache.
How should I test a page that loads inventory separately?
Identify the request that supplies the stock count. Compare its response headers and inventory revision separately from the page shell. Two cached resources can expire minutes apart.
Does a private directive tell me when a page expires?
An unqualified private directive controls storage by shared caches. It does not supply a numeric lifetime. Determine the applicable freshness policy before entering numbers.
Can I tell whether the cached object was replaced during my measurement?
Capture a validator or an application revision alongside the timestamp. If the representation changed between samples, start a fresh observation with values for the replacement.
Why can I see a validation request while the estimate still shows time left?
Request or response directives may require validation. Inspect the request that triggered the transaction and the resulting status before changing the lifetime.
How do I handle two conflicting max-age declarations?
Record the raw header and investigate the component adding the second value. A single numeric estimate cannot resolve conflicting declarations reliably.
How can I share a reproducible incident with our CDN team?
Include the request URL and variant, capture time, selected lifetime, starting age and the observed next response. Label the estimated interval separately from your measured timestamps.
How it works, with an example
Choose the lifetime for the cache you are investigating. Add elapsed seconds to the estimated age at receipt. Subtract that sum from the lifetime and floor the remaining interval at zero. Retest the same representation and record what it returns.
Practical example
A school calendar response arrives with an estimated age of 240 seconds and a five-minute lifetime. Sixty seconds later it reaches the boundary. The calculator shows 300 seconds of age and zero seconds remaining.
Additional use cases
- Time independent checks for a page shell and its inventory API.
- Schedule a retest after an event listing changes.
- Compare different edge and browser lifetimes.
Technical reference: RFC 9111 §§ 4.2–4.3 · 22.11.2026
Frequently asked questions
Do decimal minutes work?
Convert to whole seconds first. A lifetime of 2.5 minutes is 150 seconds.
Does the calculator inspect my customers’ traffic?
It runs on the numbers you supply. It has no input for accounts, logs or customer addresses.
Should I add the Age value twice across two proxies?
Use one estimated age at your chosen observation point. Adding overlapping observations can count the same elapsed time twice.
Is zero always an error?
Zero is valid for each field. A zero lifetime reaches the freshness boundary immediately.
Can the calculator predict stale-while-revalidate?
That extension permits behavior beyond the freshness boundary under defined conditions. Inspect the actual directives and cache behavior separately.
Related tools for your next step
Investigate website delivery
Request a free, no-obligation review of an example public URL and its delivery behavior.
Request a free consultation →SEOSTUDIO editorial team · Updated