Caching stores a result for reuse without repeating all computation or retrieval. On a Joomla website, it can reduce response time and server load.
Cache layers
Browsers store resources on the visitor device, proxies and CDNs store them closer to clients, and Joomla can cache component and module output. A full-page cache stores a completed response. PHP OPcache stores compiled code and serves a different purpose.
Lifetime and cache keys determine when and for whom a result can be reused. Language, query parameters, login state and other content variations matter.
Freshness
After updating Joomla data, the relevant cache may need invalidation or a resource version change. Clearing application caches does not automatically remove browser and CDN copies.
In HTTP, no-cache requires validation before reuse, while no-store prohibits storing the response. They are different directives.
What to test
Test Joomla caching for guests and signed-in users separately. Personal pages, baskets and token-based forms require suitable exclusions. A shared cache must not expose another person's data or show an outdated transaction state.
Conclusion
Caching speeds up repeated access when lifetimes, keys and exclusions are correct. Freshness and privacy checks matter as much as speed.