Collection diagnostics · FIELD GUIDE
An Age header is not the age of your analytics data
Separate proxy-cache residence from the observation window shown inside a saved report.
What the evidence can establish
MDN defines Age as time in seconds associated with an object in a proxy cache. That is a delivery-layer signal. The observation period inside an analytics report is a different fact that must come from the report data or saved evidence. A newly delivered response can contain an old reporting window, while a cached response can still contain the intended immutable historical edition. Compare the two clocks instead of collapsing them into one freshness label.
Hypothetical example: a report response has Age: 120, but the report body explicitly summarizes last week. The header describes cache residence, not a two-minute-old dataset. Conversely, a saved incident edition may remain useful precisely because it preserves last week’s observations. Decide whether the page promises a live view or a dated snapshot before calling that behavior defective.
The saved evidence used here
This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.
- c1 · Explanation and verification steps
- Age reports time in seconds associated with an object in a proxy cache. Source 1
- c2 · Explanation and verification steps
- Age is represented as a non-negative number of seconds. Source 1
The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.
AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.
What to do next
- Record the final response headers and the reporting interval visible in the page or evidence export. Keep the fetch time separate from both values.
- Identify the page contract: live dashboard, periodically refreshed summary or immutable historical edition. State the expected update behavior for that contract.
- Compare the saved evidence cutoff and publication version with the intended interval. Use Age only to investigate delivery caching, together with the relevant cache configuration.
- After a scoped correction, verify that the requested report version and observation interval are delivered. Preserve the prior historical edition when it is part of the audit trail.
How to check the result
The page and export state the same observation period, and the report explains whether it is live or historical. Delivery cache age is reported separately when relevant.
Limits of this conclusion
Age is not a complete cache-history record and does not establish when every underlying measurement was collected. This method does not imply that a dated report must always be regenerated.
This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.
Sources and publication checks
Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.
Obtained: 2026-11-03T19:30:57.869115+00:00
Location: Age header / b2; Directives / b4
Saved source fingerprint
7ee649dfe383193d46a78fdf72cc94ad43dbf15df07894edea24c3331a60df3c