- \n
- Why WordPress Databases Get Slow<\/a><\/li>\n
- What You Can Safely Remove<\/a><\/li>\n
- Back Up Your Database First<\/a><\/li>\n
- Method 1: Using a Plugin (Recommended)<\/a><\/li>\n
- Method 2: Using phpMyAdmin<\/a><\/li>\n
- Controlling Post Revisions<\/a><\/li>\n
- The Autoloaded Data Problem<\/a><\/li>\n
- Setting Up Automatic Cleanup<\/a><\/li>\n
- How to Measure the Difference<\/a><\/li>\n
- Final Thoughts<\/a><\/li>\n<\/ul>\n
Why WordPress Databases Get Slow<\/h2>\n
WordPress stores almost everything in a MySQL database: your posts, pages, comments, settings, plugin data, theme options, and user information. Every time you save a draft, WordPress creates a revision. Every spam comment that arrives gets stored. Every plugin that saves temporary data (transients) adds rows.<\/p>\n
Over months and years, this accumulates. A database that started at 5MB might grow to 200MB, with most of that being data nobody will ever use again. The database engine still has to search through all of it every time someone loads a page.<\/p>\n
Common database bloat sources:<\/p>\n
- \n
- Post revisions<\/strong> \u2014 WordPress saves every edit as a separate revision. A post edited 50 times has 50 revisions stored in the database.<\/li>\n
- Spam and trashed comments<\/strong> \u2014 Deleted and spam comments sit in the database until explicitly purged.<\/li>\n
- Expired transients<\/strong> \u2014 Temporary cached data from plugins that should have been deleted but wasn’t.<\/li>\n
- Orphaned metadata<\/strong> \u2014 Data left behind by plugins you’ve deactivated or deleted.<\/li>\n
- Pingbacks and trackbacks<\/strong> \u2014 Outdated notification data from other sites linking to yours.<\/li>\n
- Table overhead<\/strong> \u2014 Fragmentation from repeated inserts and deletes, similar to defragmenting a hard drive.<\/li>\n<\/ul>\n
What You Can Safely Remove<\/h2>\n
Not everything in the database should be touched. Some data is critical (your actual posts, pages, and settings). Other data is disposable.<\/p>\n
Safe to remove:<\/strong><\/p>\n
- \n
- Post revisions (your published content stays, only edit history is removed)<\/li>\n
- Auto-drafts (unsaved drafts WordPress creates automatically)<\/li>\n
- Trashed posts and pages<\/li>\n
- Spam comments and trashed comments<\/li>\n
- Expired transients<\/li>\n
- Trackbacks and pingbacks<\/li>\n
- Table overhead\/fragmentation<\/li>\n<\/ul>\n
Leave alone:<\/strong><\/p>\n
- \n
- Published posts, pages, and their current content<\/li>\n
- Active comments<\/li>\n
- User accounts and roles<\/li>\n
- Plugin settings and configuration<\/li>\n
- WooCommerce orders and customer data<\/li>\n<\/ul>\n
Back Up Your Database First<\/h2>\n
Before changing anything, take a backup. If something goes wrong, you want to be able to restore everything to exactly how it was five minutes ago.<\/p>\n
Most managed hosting providers (including Webfort) run daily automated backups. But for database changes, it’s worth taking a manual backup immediately before you start. You can do this through your hosting control panel’s backup tool or by exporting the database via phpMyAdmin.<\/p>\n
If your host doesn’t provide easy backups, that’s a red flag worth taking seriously. We covered what good hosting should include in our hosting checklist guide<\/a>.<\/p>\n
\n \n<\/div>\n<\/div>\n \n \n\nLooking for fast, reliable UK hosting?<\/h3>\n
Our plans start from \u00a34.99\/month<\/strong> with everything included: SSL, backups, email, and 24\/7 support.<\/p>\n View Hosting Plans \u2192<\/a>\n <\/div>\n <\/div>\n \n
Method 1: Using a Plugin (Recommended)<\/h2>\n
The safest way to clean your database is with a dedicated plugin. Two reliable options:<\/p>\n
WP-Optimize<\/h3>\n
WP-Optimize<\/a> is a free plugin that handles database cleanup, image compression, and caching. For database optimization:<\/p>\n
- \n
- Install and activate WP-Optimize from the WordPress plugin directory<\/li>\n
- Go to WP-Optimize \u2192 Database<\/strong><\/li>\n
- Review the list of optimizations (revisions, drafts, spam comments, transients, etc.)<\/li>\n
- Tick the items you want to clean<\/li>\n
- Click Run all selected optimizations<\/strong><\/li>\n<\/ol>\n
The plugin shows you exactly how many items will be removed and how much space you’ll save before you confirm anything.<\/p>\n
![\"Optimizing](\"https:\/\/images.pexels.com\/photos\/577585\/pexels-photo-577585.jpeg?auto=compress&cs=tinysrgb&w=800\")
Database optimization is one of the quickest wins for WordPress speed.<\/figcaption><\/figure>\n Advanced Database Cleaner<\/h3>\n
For more granular control, Advanced Database Cleaner<\/a> lets you inspect individual tables and identify data left behind by deleted plugins. It’s particularly useful for finding orphaned tables that other cleanup plugins miss.<\/p>\n
Method 2: Using phpMyAdmin<\/h2>\n
If you prefer working directly with the database, phpMyAdmin (available through most hosting control panels) lets you optimize tables manually.<\/p>\n
- \n
- Log into your hosting control panel and open phpMyAdmin<\/li>\n
- Select your WordPress database from the left sidebar<\/li>\n
- Click Check All<\/strong> to select all tables<\/li>\n
- From the “With selected” dropdown, choose Optimize table<\/strong><\/li>\n
- Click Go<\/strong><\/li>\n<\/ol>\n
This defragments your tables and reclaims wasted space. It’s the equivalent of the “optimize tables” button in WP-Optimize, but done manually.<\/p>\n
To delete post revisions via SQL (advanced):<\/p>\n
DELETE FROM wp_posts WHERE post_type = 'revision';<\/code><\/pre>\nOnly run SQL queries if you’re comfortable with databases and have a backup ready. One wrong query can break your site.<\/p>\n
Controlling Post Revisions<\/h2>\n
WordPress saves unlimited revisions by default. If you edit a blog post 30 times, you have 30 revisions stored permanently. For most sites, keeping the last 3-5 revisions is plenty.<\/p>\n
Add this line to your
wp-config.php<\/code> file to limit revisions:<\/p>\ndefine('WP_POST_REVISIONS', 5);<\/code><\/pre>\nThis keeps the 5 most recent revisions for each post and prevents the revision count from growing indefinitely. You can set it to
false<\/code> to disable revisions entirely, but keeping a few is safer in case you need to undo a recent change.<\/p>\nThe Autoloaded Data Problem<\/h2>\n
This is the most overlooked database performance issue. WordPress has an
options<\/code> table where plugins store settings. Some of these options are marked as “autoload”, meaning WordPress loads them on every single page request whether they’re needed or not.<\/p>\nPlugins that store large amounts of data in autoloaded options can add hundreds of milliseconds to every page load. To check your autoloaded data size, run this in phpMyAdmin:<\/p>\n
SELECT SUM(LENGTH(option_value)) AS autoload_size \nFROM wp_options \nWHERE autoload = 'yes';<\/code><\/pre>\nIf the result is over 1MB, you have autoload bloat. Common culprits are old caching plugins, analytics plugins that store data locally, and social sharing plugins. The fix is usually deactivating and deleting the problem plugin, which removes its autoloaded data.<\/p>\n
Setting Up Automatic Cleanup<\/h2>\n
Manual optimization is a one-time fix. Without automatic cleanup, the bloat returns within months.<\/p>\n
WP-Optimize includes a scheduler. Go to WP-Optimize \u2192 Settings<\/strong> and enable automatic cleanup on a weekly or fortnightly schedule. Set it to run during low-traffic hours (early morning) to avoid any brief performance impact during optimization.<\/p>\n
A reasonable automatic schedule:<\/p>\n
- \n
- Clean post revisions (keep last 5): weekly<\/li>\n
- Remove auto-drafts: weekly<\/li>\n
- Clear expired transients: weekly<\/li>\n
- Optimize tables: fortnightly<\/li>\n
- Remove spam\/trashed comments: weekly<\/li>\n<\/ul>\n
Combined with the
WP_POST_REVISIONS<\/code> limit in wp-config.php, this keeps your database lean indefinitely.<\/p>\nHow to Measure the Difference<\/h2>\n
Before running any optimization, test your site speed so you can compare the results. Three ways to measure:<\/p>\n
- \n
- Google PageSpeed Insights<\/a><\/strong> \u2014 Free, tests both mobile and desktop. Look at the Time to First Byte (TTFB) metric specifically, as that’s most affected by database performance.<\/li>\n
- Query Monitor plugin<\/strong> \u2014 Install the free Query Monitor<\/a> plugin to see exactly how many database queries each page makes and how long they take. Run this before and after optimization.<\/li>\n
- Your hosting dashboard<\/strong> \u2014 Some hosts show server response times. Check if yours does.<\/li>\n<\/ol>\n
Typical results from database optimization: 20-40% reduction in TTFB and 10-30% fewer database queries per page. For sites with heavily bloated databases, the improvement can be even larger. For more on what speed metrics to target, see our guide to website speed in 2026<\/a>.<\/p>\n
Final Thoughts<\/h2>\n
Database optimization is one of the most effective and least discussed WordPress performance fixes. It takes fifteen minutes, the risk is low (with a backup), and the results are often noticeable immediately.<\/p>\n
Clean up the bloat, limit revisions, set up automatic maintenance, and your database stays fast long-term. It’s the kind of maintenance that pairs well with server-level caching<\/a> to keep your WordPress site running at its best.<\/p>\n
If your site is still slow after optimizing the database, the issue might be your hosting rather than your WordPress setup. Slow servers, oversold shared hosting, or distant data centres all affect performance regardless of how clean your database is. Our guide to hosting types<\/a> explains the differences. And our free Website MOT tool<\/a> can help identify whether hosting performance is the bottleneck.<\/p>\n
- Query Monitor plugin<\/strong> \u2014 Install the free Query Monitor<\/a> plugin to see exactly how many database queries each page makes and how long they take. Run this before and after optimization.<\/li>\n
- Google PageSpeed Insights<\/a><\/strong> \u2014 Free, tests both mobile and desktop. Look at the Time to First Byte (TTFB) metric specifically, as that’s most affected by database performance.<\/li>\n
- From the “With selected” dropdown, choose Optimize table<\/strong><\/li>\n
- Spam and trashed comments<\/strong> \u2014 Deleted and spam comments sit in the database until explicitly purged.<\/li>\n
- What You Can Safely Remove<\/a><\/li>\n