How to Tell Whether Joomla Is Serving a Cached Page
Start with a repeatable guest request
Choose one public URL and request it while logged out. Record a small piece of content you can safely change for testing, such as article text on a staging copy. Joomla page caching is intended for guest pages, so an authenticated session is not the best test for determining whether the full-page cache is involved.
Check whether System - Page Cache is enabled
In Administrator, open System → Plugins and locate System - Page Cache. If it is enabled, Joomla can store the complete generated page and reuse it for later requests to the same URL. This is separate from the Conservative or Progressive System Cache setting in Global Configuration.
Use a controlled content change
On a staging site, or during a safe maintenance window, make a small visible change to the content behind the test URL and save it. Request the same URL again as a guest. Joomla documentation notes that changing an article does not automatically clear every full-page cache entry in which that article appears, so an unchanged guest page is a useful clue.
Inspect the Joomla page cache
When the File cache handler is in use, Joomla documentation describes Page Cache entries under the page cache group. System → Maintenance → Clear Cache can show cache groups and remove their generated cache files. If clearing the page group immediately reveals the new content, the Joomla page cache was serving the old response.
Compare logged-in and logged-out output
Request the same URL in a normal authenticated session and in a private guest session. Joomla's documented administrator-controlled caching mechanisms do not cache logged-on users in the same way. If only the guest copy remains old, that strongly narrows the investigation toward Joomla page caching or another public-facing cache layer.
Check response headers and upstream caches
A CDN, reverse proxy, hosting cache, or browser cache can also return stored HTML. Inspect the network response and any cache-specific headers supplied by those services. Clearing Joomla cannot purge an independent edge cache, so do not assume every cached response came from Joomla.
Confirm the result after cache regeneration
After clearing the relevant cache, load the page again, allow Joomla to regenerate it, and repeat the request. If the new output remains stable, document which cache layer was responsible and how it is cleared. This gives you a reliable test for future stale-page incidents.
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.