Most WordPress speed guides blame caching or image sizes for slow load times. But there is a quieter culprit that grows worse every month: database bloat.
At Rocket.net, I see this weekly. Sites with perfectly configured caching still struggle because their database tables have ballooned to 500MB, 1GB, or more. The issue is not always the size itself—it is how that bloat translates into slow queries, timeouts, and frustrated users.
Here is what actually causes database bloat, how to diagnose it, and a cleanup strategy that will not break your site.
What Database Bloat Actually Means
Your WordPress database is not just a storage container—it is an active system that grows with every action:
- Post revisions: Every autosave creates a new row
- Orphaned metadata: Deleted posts leave meta entries behind
- Transient data: Temporary cache entries that never expire
- WooCommerce sessions: Shopping cart data piles up
- Spam comments: Unfiltered junk accumulates
The wp_options table is often the biggest surprise. I have seen this single table hit 200MB+ because of plugin transients.
How to Identify Bloat (No Plugins Required)
Check Your Database Size
Most managed WordPress hosts show database size in their dashboard. Look for anything over 200MB on a standard blog, or 500MB+ on WooCommerce.
Via WP-CLI:
wp db size --tables --human-readableFind Bloated Tables
SELECT table_name, ROUND(((data_length + index_length)/1024/1024),2) AS size FROM information_schema.TABLES WHERE table_schema = DATABASE() ORDER BY size DESC;Common culprits: wp_options, wp_postmeta, wp_woocommerce_sessions
Safe Cleanup Strategy
Plugin Method: WP-Optimize (free)
- Keep last 10-20 revisions (undo insurance)
- Safe: post revisions, auto-drafts, trashed posts
- Never delete: active transients (breaks functionality)
Prevention: Add to wp-config.php:
define('WP_POST_REVISIONS', 10);Keep 10-20 revisions for safety. Zero revisions means no undo if you delete content.
When Bloat Is Not Your Problem
500MB with 50ms queries = healthy. 50MB with 5s queries = problem.
The real metric is query time, not size. Install Query Monitor (free) to check.
Need help? My speed diagnostic includes database analysis and cleanup.