Load Combined Core Block Assets
This is a workaround for sites experiencing any issues with the ability introduced in WordPress 6.9 to load block styles on demand in classic themes. The known issues have been fixed during the 7.0 release cycle with the following commits: r61076: Script Loader: Fall back to hoisting late-printed styles to end of HEAD if wp-block-library is not enqueued. r61122: Script Loader: Load block styles on demand in classic themes even when wp-block-styles support is absent. r61174: Script Loader: Improve hoisted stylesheet ordering (in classic themes) to preserve CSS cascade. r61554: Script Loader: Preserve original CSS cascade for classic themes when hoisting late-printed styles. r61945: Script Loader: Refine hoisted stylesheet ordering to preserve original CSS cascade in classic themes. If running a classic theme (i.e. not a block theme), this plugin filters should_load_separate_core_block_assets to be false. This has the effect of reverting a change introduced in 6.9 where classic themes now load separate core block assets on demand by default. Note that this plugin should be considered temporary until any issues are resolved in 7.0. At any time, you can test whether any issues remain by adding ?should_load_separate_core_block_assets=true to any frontend URL; this restores the default behavior in WP 6.9. This workaround should be temporary because there are performance benefits to loading separate core block assets. They can be loaded on demand just when they are used, as opposed to loading the large single combined wp-block-library stylesheet. Loading separate block styles on demand reduces the amount of CSS which should improve page load time. Nevertheless, as explained in the dev note, some sites may be built in a way that fundamentally does not work with loading separate block styles on demand. For these sites, this plugin is available to retain the old behavior.
Health Inspector
Health Inspector gives you a clear, honest view of what is actually happening inside your WordPress site — without touching a single byte of your data. Think of it as a medical chart for your WordPress install. It surfaces findings, flags issues, and helps you trace the root cause of problems — but it never acts without your permission. Every database query is SELECT-only. Nothing is inserted, updated, or deleted. Who it’s for Site owners who want to understand why their site is slow Developers debugging PHP errors and plugin conflicts Agencies doing pre-launch or ongoing site audits Anyone who wants to stop guessing and start knowing The Modules 🔴 Error Log Viewer PHP error log analysis — grouped, severity-rated, and sorted so you see the most important errors first. Each group shows first-seen and last-seen timestamps, occurrence count, file path, and line number. The viewer also detects whether your debug log is web-accessible and escalates the health score if so. 📅 What Changed? — Timeline Correlation The most useful debugging tool on this list. Every plugin update, activation, WordPress core update, and theme switch plotted on the same interactive timeline as your PHP error spikes. Hover any event to see correlation scores (0–99) with plain-English reasoning explaining why a change and an error are likely connected. 🗄️ DB Health Inspector Table bloat analysis, autoloaded options ranked by size, orphaned postmeta counts, Action Scheduler history, and autoload index verification. If your database is slowing you down, this is where you find out why. ⚙️ Cron Inspector Standard WP-Cron and Action Scheduler jobs in a single unified view, sorted chronologically with next-run times, intervals, and overdue highlighting. No more mystery cron tasks. 🔌 Blast Radius Analyzer Shows the full footprint of every active plugin: custom database tables, scheduled cron jobs, REST API routes, enqueued scripts and stylesheets, and hook registrations. Know exactly what a plugin owns before you deactivate it. 🚀 Update Impact Analysis Before updating any plugin, see what it shares with the rest of your site — common hooks, custom DB tables, scheduled jobs, REST endpoints, and asset bundle size — so you can anticipate conflicts before they happen. 📦 Autoload Governor Per-plugin autoload size attribution. See exactly which plugins are adding weight to every single page load, and how much. 💣 Time Bomb Detector SSL certificate expiry monitoring, PHP version risk assessment, and stale plugin flagging. Problems that tend to surface at the worst possible time — surfaced early, on your schedule. 🕵️ Plugin Abandonment Radar Every installed plugin cross-checked against the WordPress.org Plugin API for last-updated staleness, tested-up-to drift, and closed or removed status. Closed plugins are often removed for unpatched security vulnerabilities — this module tells you before it becomes a problem. 📜 Asset Inspector Every script and stylesheet WordPress has enqueued, with file sizes and running totals, separated by JavaScript and CSS. 🖥️ Server & PHP Environment php.ini directive audit, key wp-config.php constants review, PHP extension checklist, and database server details — all in one place. 📊 Hosting Benchmark On-demand database, PHP, and filesystem performance probes with letter grades and object-cache detection. ✉️ Mail Health Inspector WordPress mail transport detection, live SPF/DKIM/DMARC/MX DNS record checks, and a one-click send test that returns real failure messages instead of generic errors. 📄 Export Report Generates a self-contained, downloadable HTML diagnostic report covering the health score, database metrics, error log summary, and full system snapshot. Shareable with hosting support or a developer without granting admin access. 100% Read-Only Every query this plugin runs is SELECT-only. It reads your site’s state; it never changes it. No rows inserted, no settings modified, no plugins deactivated. Want more? WP Health Inspector Pro adds Root Cause Analysis, Conflict Detector, Request Profiler, External Dependency Monitoring, Performance Baselines, Core Web Vitals estimates, Security Audit, Content Health, and weekly Health Digest emails. Learn more at wphealthinspector.com External Services This plugin connects to the official WordPress.org Plugin API to power the Plugin Abandonment Radar module. What it does: for each installed plugin, the plugin requests that plugin’s public directory listing (last-updated date, tested-up-to version, and open/closed status) from the WordPress.org Plugin API, so it can flag plugins that appear abandoned or removed. When it happens: only when an administrator views the Plugin Abandonment Radar page. Results are cached for 12 hours between requests. Data sent: only the plugin slugs of plugins already installed on your site. No site content, user data, or personally identifiable information is sent. Service provider: WordPress.org API endpoint: https://api.wordpress.org/plugins/info/1.2/ Terms of Service: https://wordpress.org/about/terms-of-service/ Privacy Policy: https://wordpress.org/about/privacy/
