Conservative vs Progressive Caching in Joomla
Joomla's Conservative and Progressive caching modes both reduce repeated work, but they differ in how much control administrators retain over module caching. Conservative mode is generally the better starting point when a site mixes static modules with dynamic or request-sensitive output.
Where the two modes are configured
Both modes are selected under System → Global Configuration → System in the cache settings. They are distinct from the System - Page Cache plugin, which can cache an eligible complete page. When troubleshooting, identify the active layer before changing settings.
Conservative Caching gives finer module control
With Conservative Caching, supported modules can generally follow their individual caching setting. A module configured to use the global setting can participate, while a module set to no caching can be excluded. This is useful for sites where some modules are stable but others show frequently changing or visitor-sensitive information.
Progressive Caching is more aggressive
Progressive Caching handles module output more broadly and does not provide the same module-by-module selectivity. That can increase cache reuse on suitable sites, but it also means you should test menus, login-related modules, forms, personalized output, ecommerce elements, and third-party modules carefully.
Component behavior still depends on the extension
Neither mode can force an extension to cache safely. Component views and modules must cooperate with Joomla's caching APIs and their own implementation. If a third-party extension documents special cache requirements or exclusions, follow the documentation for the installed version.
Choose a mode with a controlled test
- Record the current cache configuration.
- Start with Conservative Caching when uncertain.
- Test representative pages while logged out.
- Verify dynamic modules and forms remain correct.
- Measure performance before and after the change.
- If considering Progressive Caching, switch only that setting and repeat the same tests.
A faster benchmark is not a successful configuration if visitors receive stale, personalized, or otherwise incorrect output.
Troubleshoot by isolating layers
If behavior changes after enabling a mode, clear Joomla's cache and retest with System Cache disabled. Then re-enable one mode at a time. Purge external caches separately. This isolates whether the problem belongs to Conservative/Progressive caching, Page Cache, an extension, or infrastructure outside Joomla.
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.