WPVITALS GUIDE
WordPress page caching: what WP_CACHE actually tells you
Page caching can make a WordPress site feel dramatically faster, but one setting is easy to misunderstand. The WP_CACHE constant is an indicator that a caching layer has been enabled in WordPress configuration. It is useful evidence, but it is not a complete performance test.
What page caching does
Without a page cache, WordPress usually builds a page each time a visitor requests it. WordPress loads the theme, runs queries, assembles the markup and sends the result. A page cache stores a finished response so later visitors can receive it without repeating all of that work.
This reduces PHP work and database queries. It can also lower time to first byte, especially on sites with busy homepages, large menus or expensive queries.
What WP_CACHE means
When WP_CACHE is enabled, WordPress is prepared for a page-cache drop-in. A caching plugin or hosting layer may use that flag to activate its integration. WPVitals reports the flag because it is a useful configuration check.
A missing flag does not prove that no caching exists. Some hosts cache responses at the web server or CDN layer without relying on the WordPress constant. Conversely, an enabled flag does not prove that pages are being served from cache successfully.
How to check whether caching is working
- Open the site in a private browser window and request the same page twice.
- Inspect the response headers for the cache layer used by your host or plugin.
- Confirm that logged-out visitors receive cached responses while logged-in users still see their personalized content.
- Clear the cache after a content or design change, then test again.
Do not cache everything
Account pages, carts, checkout screens and other personalized responses need different rules. A cache that serves one visitor’s private response to another is a serious configuration error. Exclusions should be deliberate and tested whenever a plugin adds cookies, sessions or user-specific output.
Where to start
Use the four performance checks that usually matter first to review images, fonts, page-level scripts and server response time before paying for a larger hosting plan. If the site needs a repeatable maintenance process, BLAC-M technical support can help document the cache rules and verify them after updates.