Enable a persistent object cache (Redis/Memcached)

Symptom

BoltAudit reports a high count of duplicate database queries per request, repeated reads of the same option or transient, or no persistent object cache backend installed. wp_using_ext_object_cache() returns false.

Impact

• Every get_option(), wp_cache_get(), or transient read goes back to the database (or the autoloaded options array) every request.
• WooCommerce in particular suffers — product, cart, and session lookups all benefit from object cache.
• TTFB on warm pages drops 20–50% on busy stores when object cache is added.

Manual fix

Requires a running Redis or Memcached server (most managed hosts offer one as an add-on; on shared hosts you may need a different tier).

1. Install Redis Object Cache (Till Krüss) or Memcached Object Cache from wordpress.org.
2. Activate. Some plugins (Redis Object Cache) require Enable Object Cache in their settings panel after activation.
3. Verify in WP Admin → Tools → Site Health → Info → "Database" → "Persistent object cache: Yes".

Apply Fix

The dashboard cannot install or configure a Redis server for you — that requires host-level work. BoltAudit can detect the need and recommend the right plugin once a backend is available; the actual server setup stays manual.

What good looks like

Object Cache: External reported by Site Health. Page-load query counts drop 40–70%, and TTFB drops by 100–300 ms on warm requests.