---
language: en
title: "Cache"
description: "Cache reuses stored data or responses to handle new requests. Understand its effect on your website, content updates, and performance evaluation."
canonical: "https://tropk.ai/en/resources/glossary/cache"
last_modified: "2026-10-12T16:09:20.180Z"
---

# Cache

Reviewed on 2026-10-07.

## What it means

Cache is the storage of data or responses for reuse in later requests. On websites, it can exist in the browser, a CDN, or the application, reducing repeated work and response time. In HTTP caching, rules and headers guide when a response can be reused or needs to be validated. Behavior depends on the layer and configuration used.

## Why it matters for marketing

For marketing, cache affects both perceived speed and the freshness of public information. A page can load quickly and still show an expired promotion. Knowing which layer is responsible helps direct the issue: editing text in the CMS does not prove that all responses already contain the new version. Expiration periods and invalidation should match the type of information.

## Example in practice

Imagine a store ends a discount in the CMS, but a visitor continues to see the old price on the homepage. The team compares the response from the origin with the response delivered by the CDN and finds different versions. They request invalidation of that page and check the public content again. They do not conclude that the database lost the edit just because the old version is still on screen.

## How to apply or check

Ask the technical lead for a map of the layers and the rules applied to the affected pages. Compare a first visit with a repeat visit, recording the URL, time, and response headers. After publishing a change, confirm that the invalidation mechanism works. Personalized content requires care with shared storage, since one user's response should not be delivered to another user inappropriately.

## Important distinctions

Cache differs from a backup, which is intended for data recovery, and is not synonymous with a CDN, which may offer other functions. In HTTP, no-cache requires revalidation before reusing the response; no-store indicates that it should not be stored. Clearing one layer does not clear all the others. Measuring a visit with a warmed cache also does not automatically represent the experience of someone accessing the site for the first time.

## Sources and references

- [HTTP caching - HTTP | MDN](<https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Caching>) — MDN Web Docs

## Continue a leitura

- [Core Web Vitals](</en/resources/glossary/core-web-vitals>)
- [HTML: the web’s markup language](</en/resources/glossary/html-the-web-s-markup-language>)
- [TTFB: Time to First Byte](</en/resources/glossary/ttfb-time-to-first-byte>)

## About the author

[Vinicius Pacheco](</en/team/vinicius-pacheco>)

Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content.

---

[All pages in Markdown](<https://tropk.ai/sitemap.md>)