Read-only database queries that surface WordPress table bloat, orphaned metadata, expired transients, and index problems — without touching a single row.
WordPress databases accumulate silent weight over time. Deleted post revisions leave behind orphaned metadata. WooCommerce order data fills tables to hundreds of megabytes. Plugins register indexes that never get used — or forget to register the ones that would help. The DB Health Inspector surfaces all of this with strictly read-only SQL queries, giving you precise data to act on without the risk of touching anything.
Lists every database table with its data size, index size, total size, and row count. Tables exceeding 50 MB are flagged. Identifies which plugins are responsible for the most WordPress database growth and where cleanup would have the biggest impact.
Reports the count of expired transients, total active transients, and oversized options (over 100 KB each) — giving you a complete picture of WordPress options table health beyond autoload data alone.
Counts orphaned postmeta, usermeta, and term relationship rows whose parent records no longer exist. Tracks WordPress revision bloat with a per-post breakdown for posts exceeding 20 revisions.
Surfaces the count of stale completed and failed Action Scheduler jobs — a common source of slow WordPress admin pages on WooCommerce and GravityForms sites.
Checks for missing indexes on commonly-queried WordPress database columns and reports on index usage statistics. A poorly-indexed database can make simple WordPress queries orders of magnitude slower.
Never. All queries are strictly SELECT statements. The module reads table statistics and row counts — it cannot write, update, delete, or truncate any WordPress data under any circumstance.
The module identifies the largest individual options and which plugin prefix they belong to. A developer can then disable autoloading using wp_update_autoload_option() in WordPress 6.4+. The plugin itself makes no changes.
An orphaned row is any row in a meta table where the parent ID no longer exists in its parent table. This happens when WordPress records are hard-deleted without proper cleanup hooks firing.
Lite shows the top-level summary — total database size, autoload total, and tables over 50 MB. Pro unlocks the full sorted table list, the complete orphaned data breakdown, the options table audit, and the revision bloat report.
Precise, actionable WordPress database diagnostics in seconds — no SQL knowledge required, no data modified.
Pro unlocks the full sorted table list, complete orphaned data breakdown, options table audit, and the revision bloat report.
Lite shows total database size, autoload total, and tables over 50 MB — completely free.
