How a persistent object cache reduces repeated database work and how to verify it safely.
Why this check matters
Object caching keeps frequently used query results available between requests. It is different from page caching and can help dynamic or logged-in areas of a busy site.
How to review it
- Confirm the host supports a persistent cache service.
- Install one compatible cache integration rather than several overlapping ones.
- Check hit rates, evictions and memory use where the service exposes them.
- Clear the cache after structural changes and test again.
Keep the change safe
A cache that is full, stale or misconfigured can make debugging harder. Document how to flush it before enabling it on production.
How WPVitals uses this signal
WPVitals checks this setting locally and reports the result in the WordPress dashboard. The check is a maintenance signal, so review the site context before changing a setting and test the visitor experience afterwards.