What is website caching?
Caching means keeping a reusable copy of information so it does not need to be fetched or generated from scratch every time. Websites can cache content in browsers, servers or delivery networks. It often improves performance, but the copies need rules about freshness and which visitors may receive them.
Useful context
- Record the changed page and when its update was published.
- Ask whether the site uses a platform, plugin or CDN cache.
How it works
Reuse saves repeated work
A café logo does not usually change on every visit. Keeping a reusable copy can reduce downloads and processing. A personal basket or order record is different because it can vary by visitor. Sensible caching distinguishes those cases rather than treating every response alike.
Freshness needs a rule
Some stored responses can be reused for a defined time; others require a check with the server. A changed page may therefore become visible differently across devices. The developer controls much of this behaviour, while browser settings can affect your own experience.
Locate the stale layer
If only your normal browser shows old content, compare a private window and record the result. If multiple people see it, the website or CDN may need investigation. These comparisons are useful clues, not proof of a specific cause.
Keep the update process predictable
Ask the maintainer how a published change refreshes the relevant cache and how it is checked. Keep the real page address and an identifiable change in the report, such as the new opening time. Avoid repeatedly clearing every system because one screenshot looks outdated.
What to check
- The approved change appears at the actual public address.
- Customer-specific information is not served as shared public content.
- The publisher knows which cache controls belong to the platform.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.