This report measures exactly what’s taking up space in your database, table by table, and tells you which of it is safe to remove, which needs a specific fix, and which is simply the legitimate cost of your actual content — rather than a generic recommendation to “clean up your database” with no sense of where the size is actually coming from.
Why size alone doesn’t tell the whole story
A large database isn’t automatically a problem; a site with years of content and thousands of orders is supposed to have a bigger database than a five-page brochure site.
This report distinguishes size that reflects real content from size that’s bloat — old revisions, orphaned data, an oversized log table — so you know which is which before deciding what, if anything, to do about it.
It’s also useful even if you’re fairly sure you already know the cause, since “probably transients” and “actually mostly Action Scheduler logs” lead to two different fixes, and guessing wrong means buying the wrong one first, then paying again once the real cause turns out to be something else entirely.
The report is also a reasonable thing to keep on file, separate from any fix you decide to buy afterwards — a documented snapshot of database health you can compare against six months or a year later to see whether bloat is building up again, or whether whatever caused it the first time has genuinely been resolved for good rather than simply gone quiet for a while before building up again later, which is a distinction a single total database size figure on its own can never actually tell you.
Database size audit & reduction report
You want to know exactly what's taking up space in your database, and whether it's genuine content or bloat, before deciding what to fix.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Database access (read-only is sufficient for the audit itself)
- Roughly how much content and how many orders, if applicable, the site actually has
- Whether backup or hosting concerns — size limits, slow exports — prompted this
- Whether you want the report only, or a quote for the fixes it identifies included
This or something else?
| You want to know what’s taking up space before deciding what to fix | This fix covers it |
| You already know it’s revisions and transients and just want it cleaned | Database cleanup – revisions, autodrafts, transients |
| You already know it’s Action Scheduler specifically | Log & Action Scheduler table truncation |
| You want general site speed measured, not just database size | Slow site diagnostic report |
| You want ongoing size monitoring, not a one-time report | Automated health check report configuration |
What we do
- Measure the size of every table in the database individually
- Identify which tables are proportionate to your actual content and which aren’t
- Break down bloat by category — revisions, transients, logs, orphaned data
- Estimate how much space each category of cleanup would actually recover
- Flag anything requiring its own separate fix rather than a general cleanup
- Deliver findings in plain language with a clear priority order
What is included
- A table-by-table breakdown of database size
- Bloat categorised and quantified, not just flagged generically
- An estimate of space recoverable from each category
- A written report you can act on yourself or bring back to us
Not included
- Performing the cleanup itself, which is quoted separately based on findings
- Ongoing size monitoring
- Auditing custom application databases outside WordPress’s own tables
- A guarantee of a specific final database size
Questions about this fix
My hosting dashboard already shows a database size number. Isn't that enough?
That number tells you the total, not what's in it or whether it's a problem. This report breaks it down by table and category, which is what actually tells you whether to act and on what.
Will this slow down my site while it runs?
No, this is a read-only audit — we're measuring what's there, not changing anything, so there's no risk to the live site during the report itself.
What if most of the size turns out to be legitimate content?
Then we say so — the point of the report is an honest answer, not a justification for a cleanup you don't need. Some sites are simply large because they have a lot of real content.
Can this tell me if my backups are slow because of database size?
Yes, that's exactly the kind of question this answers — whether backup time correlates with genuine content size or with bloat that's inflating export time unnecessarily.
Do I have to buy the cleanup fix afterwards?
No, the report stands alone, and some findings are things you or your host can act on directly without needing us to do the work.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.