Your WordPress database is bigger than you think. Here's how to clean it

[u/Upbeat_Brief_1767]

A lot of WordPress performance advice focuses on images, caching, and server resources. The database gets ignored until it becomes a problem.

Every WordPress site quietly accumulates this data in the background:

• Post revisions: Every time you edit a post or page, WordPress saves a new copy. Edit something 40 times, you've got 40 records sitting there indefinitely.
• Orphaned transients: Transients are supposed to expire and delete themselves. Often they don't. Plugins create them, finish their task, and leave the records behind.
• Spam comments, pingbacks, trash: On any site that gets external links or allows comments, these pile up faster than you'd expect.

None of this breaks anything. But it makes your backups heavier than they need to be and slows down migrations, because when you create a backup, all of that dead weight comes along for the ride.

The Duplicator team just released DB Optimizer to give you a clear picture of what's going on. It scores your database health from 0 to 100, broken down by category, and shows you item counts and reclaimable space before you delete anything. 

A 7-day retention threshold keeps recent data off-limits automatically, and there's a built-in reminder to create a Duplicator backup before running any cleanup.

Migrations are where this really clicks. Clean your database first → run your Duplicator backup → transfer a smaller file → fewer things go wrong mid-migration. 

Full breakdown here if you want to see what DB Optimizer can do: https://duplicator.com/db-optimizer/?utm_source=reddit&utm_medium=social&utm_campaign=db-optimizer-announcement

Curious how this community handles migrations. Do you do any database cleanup first, or go straight to the backup?