BerqWP 4.1.10 ships two new tabs inside the plugin settings: Database and Debloat. They cover two jobs that, until now, most site owners handled with a separate plugin like WP-Optimize or Perfmatters. Now they sit alongside BerqWP’s caching, Critical CSS, and image optimization, so your whole performance stack lives in one place.
The Database tab cleans up the clutter that builds up in your WordPress database over time. The Debloat tab strips out background WordPress features you probably don’t need. Neither one requires configuration to get started, and both are safe by default.
TL;DR: BerqWP 4.1.10 adds native WordPress database optimization (revisions, transients, spam, table optimization, with optional scheduling) and a Debloat tab (Heartbeat API control plus toggles for emojis, embeds, XML-RPC, and head cleanup). Everything is off or set to defaults until you turn it on, except emojis, which are disabled out of the box.
Why Database Optimization and Debloat Belong in One Plugin
A slow WordPress site is rarely slow for one reason. It’s usually a stack of small things: a bloated database, background HTTP requests you don’t need, scripts loaded on every page that serve no purpose. Caching and Critical CSS handle the front end. The Database and Debloat tabs handle the rest.
Until now, that “rest” meant installing another plugin. WP Rocket ships its own database cleanup. Perfmatters built its reputation on debloating. Both are good at what they do, but they’re another plugin to license, update, and configure. If you’re already running BerqWP for caching and Core Web Vitals, the new tabs let you consolidate instead of stacking tools. You can see how BerqWP stacks up in our BerqWP vs WP Rocket and BerqWP vs Perfmatters comparisons.
This release follows the same direction we set with the BerqWP v4 release: one plugin that handles the full performance picture, from server-side cache delivery to the database underneath it.
WordPress Database Optimization, Now Built Into BerqWP
Every WordPress site accumulates database junk. Post revisions pile up. Auto-drafts sit there forever. Expired transients never get cleared. Spam comments linger. Over months and years, this bloat slows down database queries, which in turn slows down your server response time and everything built on top of it.
The new Database tab gives you manual cleanup actions and an optional scheduler.
Cleanup Actions (Run Anytime)
Each action runs on demand with one click and reports how many items it cleaned up. Nothing here runs automatically unless you also turn on Scheduled Optimization below.
| Action | What it does | Configuration |
|---|---|---|
| Post revisions | Cleans up old revisions, keeping only the most recent ones | Keeps the last 5 by default, you can change this number |
| Auto-drafts & trashed posts | Removes leftover auto-saved drafts and posts sitting in the trash | No options |
| Expired transients | Clears out expired temporary cache data | No options |
| Spam & trashed comments | Removes spam and trashed comments | No options |
| Orphaned post meta | Cleans up leftover data from deleted posts | No options |
| Optimize database tables | Optimizes your database tables for better performance | No options |
Run these whenever your site feels sluggish or after a big content cleanup. The post revisions action is the one most sites benefit from most, especially blogs with years of edits.
Scheduled Optimization
If you’d rather not remember to run cleanup manually, Scheduled Optimization handles it for you.
- Enable/disable: Off by default. You turn it on for anything to run automatically.
- Frequency: Daily, Weekly, or Monthly. Weekly is selected by default.
- Tasks to run on schedule: Pick which cleanup actions run automatically. Post revisions, Expired transients, and Spam & trashed comments are pre-selected by default. The rest stay off until you enable them.
- Last Run: See how long ago the schedule last ran.
- Next Run: See when the next scheduled cleanup will happen.
The defaults are conservative on purpose. Weekly is frequent enough to keep bloat in check without hammering your database, and the three pre-selected tasks are the safest, highest-value cleanups.
Debloat WordPress: Strip Out What You Don’t Need
The Debloat tab targets the background WordPress behavior that loads on every page whether you use it or not. Two sections: Heartbeat API control and a set of feature toggles.
Heartbeat API Control
WordPress uses the Heartbeat API to “check in” with your server in the background, for things like autosave and the “another user is editing this post” warning. On some hosting setups, especially shared hosting, that periodic check-in adds avoidable load.
The default setting is Default (no changes), meaning Heartbeat behaves exactly as WordPress normally does. Your options:
- Default (default setting): no changes.
- Restrict to post editor only (recommended): Heartbeat only runs while you’re actively editing a post, reducing background activity everywhere else.
- Throttle interval everywhere: keep it running, but less frequently. You set the interval, default 60 seconds if this mode is selected.
- Disable completely: turns it off entirely. Note that this also disables autosave and the “another user is editing” warnings.
The recommended option, restrict to post editor only, is the sweet spot for most sites. You keep autosave where it matters and cut the background noise everywhere else.
Feature Toggles
Simple on/off switches to disable WordPress functionality you don’t need. All of these are off by default, meaning the feature stays enabled and unchanged, except Emojis, which is disabled by default.
| Feature | What disabling it does | Default |
|---|---|---|
| Emojis | Stops loading the emoji script that WordPress adds to every page | Disabled by default |
| Embeds | Turns off the ability to embed your posts on other sites, and removes related scripts | Off |
| XML-RPC | Disables an older remote-access feature that’s rarely needed and often targeted by attackers | Off |
| REST API Discovery Link | Removes a technical link from your page’s <head>. Your site’s REST API keeps working normally. | Off |
| Head Cleanup | Removes a few unused technical tags from your page’s <head> section | Off |
| Self Pingbacks | Stops WordPress from creating a comment on your own post when you link to another post on your own site | Off |
Emojis being disabled by default is the one opinionated choice here. WordPress loads an emoji polyfill script on every single page, front and back, and almost no site actually needs it. Turning it off is a free, zero-risk win, so we turned it on for you.
The rest we leave to your judgment. XML-RPC is worth disabling if you don’t use the mobile app or external publishing tools. Head Cleanup and the REST API Discovery Link are small, safe reductions in page weight. Self Pingbacks is a quality-of-life toggle for anyone tired of self-referencing comment notifications.
How to access the New Tabs
Both tabs live in your BerqWP settings, under the same screen you already use for caching and optimization.
- Update BerqWP to 4.1.10 or later.
- Open BerqWP Settings and switch to the Database tab.
- Run any cleanup action on demand, or enable Scheduled Optimization and pick your frequency and tasks.
- Switch to the Debloat tab.
- Choose your Heartbeat API setting and toggle off any features you don’t use.
There’s no required order. You can debloat first, clean the database first, or do both at once. None of these actions conflict with BerqWP’s caching or image optimization. For the broader picture of how everything fits together, see our BerqWP best practices guide.
What This Means for Core Web Vitals
Database optimization and debloating don’t show up in a Lighthouse report the way a large image or a render-blocking script does. Their effect is upstream. A leaner database means faster query responses, which means a lower server response time, which feeds directly into your LCP and your overall Core Web Vitals scores. Fewer background requests and head tags mean less work for the browser on every page load.
Stack these tabs on top of BerqWP’s existing caching, Critical CSS, and image conversion, and you’ve covered the full performance stack from database to rendered pixel. See the complete feature list for everything BerqWP handles.
What’s Next
4.1.10 is a focused release: two tabs, one job each, both safe by default. We’re already working on the next round of improvements. If you want to follow along, the changelog tracks every release.
If you’re not running BerqWP yet, you can get started here. Existing users, just update to 4.1.10 from your WordPress dashboard.
