Redis Object Cache drops in wp-content/object-cache.php to back WordPress's own internal object cache — transients, query caching — with Redis instead of per-request PHP memory. It has zero public execution surface and zero effect on a static build's output: it only ever speeds up WordPress itself while WordPress is running (admin screens, the crawler's own render pass during a build), never something a visitor's request depends on once a page is served statically.
Like Object Cache Pro, this operates at the object-cache layer, not the page-cache layer — it speeds up WordPress itself (queries, transients) while WordPress is running, with no effect on, or conflict with, Static Shield's own static output.
No single mode applies — Redis Object Cache doesn't influence which serving mode a site should use; see the notes below for what it actually does.
Every page is served from the static release exactly as it would be without this plugin — the object cache never touches page output.
None — this is a backend-only drop-in with no public routes or execution surface of its own; it's compatible with any Static Shield mode, including Zero-WordPress/Vault, since it only matters while WordPress is actually running.
None needed — Redis Object Cache declares no public routes of its own.
No special setup — detected automatically once active.
Nothing specific to Static Shield — an unreachable Redis server can make WordPress itself error, but that's a pre-existing operational concern of running this plugin at all, not something Static Shield introduces or changes.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp