DevLemon Cache Observatory

DevLemon Cache Observatory is a read-first cache diagnostics workspace for WordPress administrators and developers.

Instead of acting as another cache optimizer, it focuses on explaining the cache state that already exists on the site. It combines object-cache diagnostics, cross-request persistence testing, cache drop-in inspection, transient analysis, environment checks, and a local diagnostic report without installing Redis, changing wp-config.php, editing .htaccess, or altering another plugin’s configuration.

What makes it useful

• Cross-request persistence test — verifies whether an object-cache value survives a separate request instead of relying only on plugin detection.
• Object cache inspection — reports WordPress object-cache availability and the state returned by wp_using_ext_object_cache().
• Drop-in inventory — checks object-cache.php and advanced-cache.php without modifying them.
• Transient inspector — search, filter, sort, and review expiration state before choosing a deletion action.
• Safe cleanup controls — delete one transient, selected transients, or expired transients only. No automatic cleanup is performed.
• Environment snapshot — WordPress, PHP, memory, WP_CACHE, multisite, and detected cache-related plugins in one place.
• Local diagnostic report — produces a copyable plain-text report without credentials, secrets, telemetry, or remote API calls.
• Explicit cache flush — wp_cache_flush() is available only as an administrator action with nonce validation and confirmation.

Safety model

The plugin is read-only by default. Any action that changes cache data requires an authenticated administrator, a WordPress nonce, and explicit user interaction.

DevLemon Cache Observatory never installs cache drop-ins, never enables or disables a cache plugin, never modifies wp-config.php or .htaccess, and never sends diagnostic data to an external service.

Privacy

No telemetry, analytics, tracking pixels, advertising, remote APIs, or external assets are used. Inspection and diagnostics remain inside the WordPress installation.