How Joomla Caching Works

Joomla caching improves performance by reusing previously generated output or calculated results instead of rebuilding everything for every eligible request. Joomla can cache at several layers, and the behavior depends on the caching mode, the extension being rendered, and whether the visitor is eligible for that cache.

Understand what a cache is doing

Without caching, Joomla may repeat database queries, extension processing, module rendering, and page generation for similar requests. A cache stores reusable results for a period of time. Later eligible requests can use that stored result, reducing repeated work.

Caching does not replace the database or permanently change article content. Cached data is temporary and can be expired or cleared.

Know Joomla's main administrator-controlled cache layers

Joomla provides page caching as well as Conservative and Progressive caching modes. Page caching can reuse a whole eligible page. Conservative and Progressive caching operate at component-view and module levels according to Joomla's caching rules and each extension's implementation.

Because these mechanisms cache at different scopes, enabling more than one layer can change where stale output originates. Diagnose one layer at a time.

Conservative and Progressive caching differ in control

With Conservative Caching, cacheable modules can generally follow their individual caching settings, allowing more selective control. Progressive Caching is more aggressive about reusing module output and is less selective at the individual-module level.

Neither mode can make an extension cache correctly if that extension's output is inherently dynamic or its implementation does not support the expected caching behavior.

Cache lifetime controls how long results can be reused

Joomla's cache settings include a lifetime that determines how long cached entries remain eligible for reuse. Some extensions or modules can expose their own cache controls as well. A longer lifetime can improve reuse but also increases the period during which a changed page may appear stale to an eligible visitor.

Other systems can cache Joomla too

A Joomla site may also sit behind PHP OPcache, a web-server cache, hosting cache, reverse proxy, CDN, or browser cache. Those are separate from Joomla's own cache storage. Clearing Joomla's cache will not necessarily purge Cloudflare, a host-level full-page cache, or a visitor's browser.

When content stays stale after Joomla's cache is cleared, identify every caching layer in the request path before changing Joomla settings repeatedly.

Test caching safely on the actual site

  1. Record the current cache configuration.
  2. Enable or change one caching layer at a time.
  3. Test representative guest pages, modules, forms, and dynamic areas.
  4. Make a harmless content change and verify when it becomes visible.
  5. Clear the relevant cache and confirm the expected output returns.
  6. Check personalized or access-controlled areas before considering the configuration complete.

The right cache configuration is the one that improves performance without serving incorrect or stale output for the site's actual extensions and traffic patterns.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.

Open a Support Ticket