Dhanendran Rajagopal

Upgrade Readiness Monitor tells you whether a site is safe to upgrade before you bump PHP or WordPress — and exactly what to fix if it isn’t.
It works in three complementary ways:
<ul>
<li>
Real-time deprecation capture. The plugin listens for WordPress’s deprecation signals (<code>deprecated_function_run</code>, <code>deprecated_hook_run</code>, <code>doing_it_wrong_run</code>, and friends) as your site runs. Because those signals fire regardless of <code>WP_DEBUG</code>, you catch real deprecations on production without turning on debug mode — each one attributed to the plugin or theme that triggered it.
</li>
<li>
Plugin & theme audit. A one-click scan checks every installed plugin and your active theme against WordPress.org for abandoned code (no update in 2+ years), “tested up to” lag, available updates, and declared PHP requirements.
</li>
<li>
Static code scan against your chosen target. Every plugin and theme — including custom and premium code that isn’t on WordPress.org — has its PHP parsed and checked against the WordPress and PHP versions you plan to upgrade to. Findings are graded Error (will break — e.g. a function removed in the target PHP version) or Warning (a deprecation notice you’ll start seeing). The functions the target WordPress version deprecates are read from WordPress core itself, so results reflect the actual upgrade.
</li>
</ul>
Everything rolls up into a single green / amber / red readiness verdict, and a target selector lets you choose exactly which WordPress and PHP versions you’re upgrading to.
<h4>Built for developers and agencies</h4>
<ul>
<li>No configuration — install, choose your target, and scan.</li>
<li>Read-only and safe: it never changes your site.</li>
<li>The audit runs in the background in small chunks, so it never blocks or slows a page load.</li>
<li>WP-CLI included: <code>wp readiness check</code> prints the full report and exits non-zero on a red verdict, so you can gate upgrades in CI/staging.</li>
</ul>
<h4>WP-CLI</h4>
<pre><code># Full readiness report
wp readiness check

# Machine-readable output for pipelines
wp readiness check --format=json
</code></pre>
<h3>External services</h3>
This plugin connects to WordPress.org to assess upgrade readiness. It does not contact any other third-party service and does not send any personal data.
<ol>
<li>WordPress.org Plugins/Themes API (api.wordpress.org) — for each installed plugin and theme, its slug is sent to look up the latest version, “tested up to” value, and last-updated date. Used during a scan and the weekly background scan.</li>
<li>WordPress.org version list (api.wordpress.org/core/stable-check) — fetches the list of available WordPress versions to populate the upgrade-target selector.</li>
<li>WordPress.org core source (core.svn.wordpress.org) — downloads the target WordPress version’s public list of deprecated functions to compare against your code. Only the version number is part of the request.</li>
</ol>
All three are WordPress.org services, governed by the WordPress.org privacy policy (https://wordpress.org/about/privacy/).

Upgrade Readiness Monitor

Know what will break before you upgrade PHP or WordPress — real-time deprecation capture plus a plugin and theme compatibility audit.

Foysal Zihak

Health Radar is a comprehensive WordPress plugin auditing and health monitoring tool for site administrators. Get a clear, real-time picture of their site’s plugin ecosystem—conflicts, performance bottlenecks, compatibility issues, and errors—without guessing or digging through logs.
Stop managing plugins blindly. Stop performance issues before they impact your users. Stop compatibility problems from becoming critical failures.
Core Features:
<ul>
<li>
🔍 Plugin Conflict Detector — Instantly detects duplicate script and style handles, identifies hook collisions between active plugins, and highlights which plugins are fighting for the same resources.
</li>
<li>
⚡ Performance Insight Panel — Measures total enqueued assets, calculates JS/CSS payload, counts database queries (when SAVEQUERIES enabled), audits wp_options autoload bloat, and generates a 0–100 health score with actionable recommendations.
</li>
<li>
🐘 PHP Compatibility Checker — Validates each plugin’s Requires PHP header against your server version, scans for deprecated WordPress function usage, and flags incompatible plugins before they break your site.
</li>
<li>
📋 Debug Log Analyzer — Intelligently parses wp-content/debug.log, categorizes errors as fatal, warnings, or notices, attributes errors to specific plugins via stack trace analysis, and shows trends over time.
</li>
<li>
🧬 Duplicate Asset Detector — Uses file fingerprinting (MD5) to identify identical JavaScript and CSS libraries loaded by multiple plugins (detects jQuery, Lodash, Moment.js, Chart.js duplicates, and more).
</li>
<li>
📄 Health Report Generator — Compiles a full site health snapshot into a single printable page; export as JSON for automation, or generate PDF from browser print dialog.
</li>
</ul>
WP-CLI Integration:
Automate plugin health audits and reporting via command line:
<ul>
<li><code>wp healthmonitor scan</code> — Trigger a full plugin health scan and display results.</li>
<li><code>wp healthmonitor score</code> — Get your current health score (0–100) instantly.</li>
<li><code>wp healthmonitor conflicts</code> — List all detected plugin conflicts and collisions.</li>
<li><code>wp healthmonitor report</code> — Generate a complete health report in table format.</li>
<li><code>wp healthmonitor report --format=json</code> — Export full report as JSON for programmatic access and dashboards.</li>
<li><code>wp healthmonitor log --last=50</code> — Display recent debug log entries (customizable number).</li>
</ul>
Perfect for scheduled audits, CI/CD integration, and headless WordPress monitoring.
Who Should Use Health Radar?
<ul>
<li>WordPress Site Administrators — Take control of your plugin ecosystem.</li>
<li>Web Hosting Providers — Offer health audits to your clients as a value-add service.</li>
<li>WordPress Developers & Agencies — Audit client sites, debug complex plugin interactions, optimize performance.</li>
<li>WP-CLI Power Users — Integrate plugin audits into automation workflows and monitoring scripts.</li>
</ul>
Security & Privacy First:
This plugin operates with zero external dependencies and complete data privacy:
<ul>
<li>✅ No external HTTP requests — All analysis happens locally on your server.</li>
<li>✅ No telemetry or tracking — We don’t collect usage data.</li>
<li>✅ No data transmission — Your plugin list, errors, and reports never leave your site.</li>
<li>✅ WPCS & Security Compliance — Follows WordPress Coding Standards and best practices.</li>
<li>✅ WP_Filesystem API — Uses WordPress’s secure file operations, never direct fopen/fread.</li>
<li>✅ Nonce-protected AJAX — All admin actions verified with WordPress security tokens.</li>
<li>✅ Capability Checks — Only administrators (manage_options) can run scans or view reports.</li>
</ul>
<h3>System Requirements</h3>
<ul>
<li>WordPress: 6.3 or newer</li>
<li>PHP: 8.1 or newer (object-oriented PHP with type hints)</li>
<li>Database: MySQL 5.7+ or MariaDB 10.2+</li>
<li>Recommended: WP_DEBUG enabled during audits for maximum visibility</li>
</ul>
<h3>Performance & Compatibility</h3>
Performance Impact: 
* Zero performance impact on front-end 
* Admin dashboard scans: 1–3 seconds (depending on plugin count) 
* Results cached for 1 hour 
* No background processes or cron jobs
Tested Compatibility: 
* ✅ WordPress 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9+ 
* ✅ PHP 8.1, 8.2, 8.3, 8.4 
* ✅ All major hosting providers (Kinsta, WP Engine, Bluehost, SiteGround, etc.) 
* ✅ Multisite WordPress installations 
* ✅ WP-CLI compatible

Health Radar

Detect plugin conflicts, performance issues, PHP compatibility risks, and debug log errors from your WordPress dashboard.

Upgrade Readiness Monitor vs Health Radar