Title: CB Site Health & Debug Author: Chris M Ybanez Published: September 21, 2026 Last modified: September 21, 2026 --- Search plugins ![](https://ps.w.org/cb-site-health-debug/assets/banner-772x250.png?rev=3705831) ![](https://ps.w.org/cb-site-health-debug/assets/icon-256x256.png?rev=3705831) # CB Site Health & Debug By [Chris M Ybanez](https://profiles.wordpress.org/chrismaryey02/) [Download](https://downloads.wordpress.org/plugin/cb-site-health-debug.1.0.2.zip) * [Details](https://wordpress.org/plugins/cb-site-health-debug/#description) * [Reviews](https://wordpress.org/plugins/cb-site-health-debug/#reviews) * [Installation](https://wordpress.org/plugins/cb-site-health-debug/#installation) * [Development](https://wordpress.org/plugins/cb-site-health-debug/#developers) [Support](https://wordpress.org/support/plugin/cb-site-health-debug/) ## Description CB Site Health & Debug is a two-part tool for developers and site owners who want to know _why_ a page is slow and _what_ to fix, without digging through server logs. **1. Front-end debug bar** A toolbar item (visible only to logged-in administrators) that opens a panel showing, for the exact page you’re looking at: * Database queries, with timing and the code that triggered each one (requires ` SAVEQUERIES`) * Hooks and actions fired, with counts * `_doing_it_wrong()` calls and deprecated function/argument/hook usage * PHP notices, warnings, and errors * Outbound HTTP API calls and their response times * Enqueued scripts and styles, with handles, sources, versions, and dependencies * Loaded text domains, transient writes, and capability checks * WordPress lifecycle timing (plugins_loaded init template_redirect footer) * Template hierarchy and conditional tags * A custom `cbdd_log( $value )` helper you can call from your own code to send values to the panel, the same way you’d use `error_log()` **2. Site Health & Debug report (Tools menu)** A page that scans your site for common performance and configuration problems and rates each one Good / Warning / Needs Fixing, with a plain-English explanation and a fix — covering PHP/server settings, database bloat (autoloaded options, revisions, expired transients), caching (object cache, page cache), overdue cron events, unoptimized images, and — when WooCommerce is active — Action Scheduler backlogs. It also includes: * **One-click cleanup** — remove expired transients, delete old post revisions, clear the slow-query log * **Slow query log** — queries over a configurable threshold are saved across visits, not just the current page load * **History & trend** — a daily snapshot shows what’s newly failing or fixed since the last check, and a 10-day trend table * **Admin menu badge** — a red count bubble on the Tools menu when critical issues exist, refreshed daily even if nobody opens the page * **Optional weekly email digest** — a summary of critical/warning findings sent to an address you choose Everything is restricted to users with the `manage_options` capability. Nothing runs for site visitors, and no data leaves your site — there is no external service, tracking, or license check involved. ## Screenshots [⌊The CB Site Health & Debug performance report, showing status badges and fixes.⌉⌊ The CB Site Health & Debug performance report, showing status badges and fixes.⌉[ The CB Site Health & Debug performance report, showing status badges and fixes. [⌊The front-end debug bar panel.⌉⌊The front-end debug bar panel.⌉[ The front-end debug bar panel. ## Installation 1. Upload the plugin files to `/wp-content/plugins/cb-site-health-debug`, or install it through the WordPress Plugins screen directly. 2. Activate the plugin through the “Plugins” screen. 3. Open **Tools CB Site Health & Debug** for the performance report, or look for the debug bar in the admin toolbar as a logged-in administrator. 4. (Optional) Add `define( 'SAVEQUERIES', true );` to `wp-config.php` to enable database query capture in the debug bar and the slow query log. ## FAQ ### Will this slow down my site for visitors? No. Every part of the plugin checks `current_user_can( 'manage_options' )` before doing anything, so regular visitors and non-admin users never trigger any of its collectors. ### Why don’t I see any database queries? Query capture requires `SAVEQUERIES` to be enabled in `wp-config.php` — the same requirement WordPress core itself imposes for this data. The plugin will tell you when it’s off instead of showing nothing silently. ### Does the performance report run on every page load? No. It only runs when you open Tools CB Site Health & Debug, plus a lightweight daily WP-Cron check that refreshes the admin-menu badge and trend history. ### Does this send any data outside my site? No, unless you turn on the optional weekly email digest, which uses your site’s own `wp_mail()` to send to an address you configure. There is no external analytics, license server, or third-party service involved. ### What happens to the data if I delete the plugin? Deleting it through the Plugins screen removes its settings and its two small database tables (the slow-query log and the health-check history). Deactivating alone does not delete anything. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “CB Site Health & Debug” is open source software. The following people have contributed to this plugin. Contributors * [ Chris M Ybanez ](https://profiles.wordpress.org/chrismaryey02/) [Translate “CB Site Health & Debug” into your language.](https://translate.wordpress.org/projects/wp-plugins/cb-site-health-debug) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/cb-site-health-debug/), check out the [SVN repository](https://plugins.svn.wordpress.org/cb-site-health-debug/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/cb-site-health-debug/) by [RSS](https://plugins.trac.wordpress.org/log/cb-site-health-debug/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.2 * Removed the duplicate “Tested up to” plugin header (this value belongs only in readme.txt, per WordPress.org guidelines). * Corrected the Contributors list to use the correct WordPress.org username. #### 1.0.1 * Code-quality pass: proper prefixing on the internal class/function names, cache- busting version added to registered assets, superglobal values sanitized before use, and all custom-table SQL now uses prepared identifier placeholders instead of direct string interpolation. #### 1.0.0 * Initial public release. ## Meta * Version **1.0.2** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.4 or higher ** * Tested up to **7.1.2** * PHP version ** 7.4 or higher ** * Tags * [debug](https://wordpress.org/plugins/tags/debug/)[performance](https://wordpress.org/plugins/tags/performance/) [query monitor](https://wordpress.org/plugins/tags/query-monitor/)[site health](https://wordpress.org/plugins/tags/site-health/) [woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/cb-site-health-debug/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/cb-site-health-debug/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/cb-site-health-debug/reviews/) ## Contributors * [ Chris M Ybanez ](https://profiles.wordpress.org/chrismaryey02/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/cb-site-health-debug/)