Every WordPress site accumulates database bloat over time. Post revisions, auto-drafts, expired transients, spam comments, and orphaned meta data pile up month after month. As your database grows, queries take longer, which increases your server response time and slows down your entire site. BerqWP 4.1.10 adds a Database tab so you can handle this cleanup natively, without installing a separate plugin.
TL;DR: BerqWP’s Database tab lets you clean up post revisions, auto-drafts, expired transients, spam comments, orphaned post meta, and optimize database tables. You can run cleanup on demand or schedule it to run automatically on a daily, weekly, or monthly basis.
Why Your WordPress Database Gets Bloated
WordPress stores a lot more than your published content. Every time you edit a post, WordPress saves a full copy as a revision. Drafts you started but never published sit in the database as auto-drafts. Transients, which are temporary cache entries, often expire but never get removed. Spam comments accumulate even if you never approve them. When you delete a post or uninstall a plugin, leftover metadata often stays behind as orphaned records that nothing references anymore.
Over months and years, these leftovers add up. A site that has been running for a few years can easily have thousands of revisions and expired transients taking up space. Every database query has to sift through this extra data, which means slower responses and higher server load. This is why wordpress database optimization matters even on a well-cached site. Caching reduces how often the database is queried, but it does not make the queries themselves faster when they do run.
Here is a concrete example. If you have 200 posts and edit each one an average of 10 times, you have roughly 2,000 revisions stored in your database. None of those revisions serve your visitors. They exist only so you can restore an earlier version if needed, and most of them you will never look at again. Multiply that by expired transients from plugins, spam comments caught by Akismet, and orphaned meta from plugins you uninstalled years ago, and you can see how the bloat builds.
Manual Cleanup Actions
The Database tab gives you six cleanup actions. Each one runs on demand with a single click and reports exactly how many items were cleaned. Nothing runs automatically unless you enable Scheduled Optimization.
| Action | What It Does | Configuration |
|---|---|---|
| Post revisions | Cleans up old post revisions | Keeps last 5 by default, configurable |
| Auto-drafts and trashed posts | Removes leftover drafts and trashed posts | No options |
| Expired transients | Clears expired temporary cache data | No options |
| Spam and trashed comments | Removes spam and trashed comments | No options |
| Orphaned post meta | Cleans leftover data from deleted posts | No options |
| Optimize database tables | Optimizes tables for better performance | No options |
Post revisions is the only action with a configurable setting. By default it keeps your five most recent revisions per post and removes the rest. You can adjust this number if you want to keep more or fewer revisions for safety. The other five actions have no configuration because they remove data that has no ongoing value. Expired transients, spam comments, and orphaned meta are safe to remove in full.
After you run an action, the tab reports how many items were cleaned. For example, you might see that 1,847 expired transients were removed, or that 312 spam comments were deleted. This gives you a clear picture of how much bloat had accumulated and confirms the cleanup actually ran.
Scheduled Optimization
Scheduled Optimization runs your chosen cleanup tasks automatically so you do not have to remember. It is off by default, so nothing happens until you turn it on.
When you enable it, you pick a frequency: Daily, Weekly, or Monthly. Weekly is the default, and it is the right choice for most sites. It is frequent enough to keep bloat from building up without putting unnecessary load on your database every day.
You also choose which tasks run on schedule. Three tasks are pre-selected by default: Post revisions, Expired transients, and Spam and trashed comments. These are the safest, highest-value cleanups. They remove data that has no long-term value, so running them regularly carries essentially no risk. You can add or remove tasks from the schedule at any time.
The scheduler shows you the Last Run and Next Run times so you can confirm it is working. If you ever want to run a cleanup outside the schedule, the manual actions are always available and run independently. This is useful if you just did a major content cleanup or uninstalled several plugins and want to clear the leftover data immediately rather than waiting for the next scheduled run.
How to Use the Database Tab
- Update BerqWP to 4.1.10 or later.
- Open BerqWP Settings and switch to the Database tab.
- Run any cleanup action on demand by clicking it, or enable Scheduled Optimization and pick your frequency and tasks.
That is it. The tab reports results after each run so you can see exactly what was cleaned and how many items were removed. If you enable Scheduled Optimization, you can close the tab and let it run on its own. Come back anytime to check the Last Run and Next Run indicators.
How Database Optimization Affects Core Web Vitals
A leaner database means faster query responses. When your database does not have to sift through thousands of expired transients and old revisions, it returns results faster. That means a lower server response time, which directly feeds into your Largest Contentful Paint and your overall Core Web Vitals scores.
Database optimization is not a silver bullet on its own. It works alongside caching, Critical CSS, and image optimization. Think of it as removing friction from the foundation. Caching means the database is queried less often, but when a cache miss happens or a logged-in user visits, a lean database responds faster than a bloated one. For the full picture, review the BerqWP best practices guide and the complete feature list to see how everything fits together.
