Non-persistent object cache

Problem Summary

Non-persistent object cache means WordPress caches objects only during the current request. The same queries and calculations happen again on the next page load.

Performance Impact

• More database queries: Results are not reused across requests
• Slower admin pages: Dashboards and editors repeat expensive lookups
• Weaker dynamic performance: Logged-in and ecommerce pages cannot rely only on page cache

How to Detect

1. Site Health: WordPress may recommend persistent object cache
2. Query Monitor: Check repeated queries on dynamic pages
3. Object cache status: Verify whether a backend like Redis is active

Solutions

1. Install Redis or Memcached

Use a persistent backend supported by your hosting environment.

2. Add a WordPress Drop-In

A plugin or custom drop-in connects WordPress to the cache server.

3. Monitor Hit Rate

Persistent cache only helps when hit rate is meaningful and evictions are controlled.

4. Combine With Page Cache

Object cache supports dynamic work; it does not replace full page caching for public pages.