WooCommerce stores slow down over time from database bloat, not traffic — and checkout usually feels it first. Here’s what to clean, and how often.
The short version
- WooCommerce stores slow down over time mainly because of database bloat, not traffic.
- Abandoned carts, post revisions and transients accumulate silently in the background.
- Checkout is usually the page that suffers first, because it queries the most tables.
- A recurring cleanup schedule prevents the slowdown from ever becoming visible to customers.
A WooCommerce store that felt fast at launch often feels sluggish a year later — not because traffic grew beyond
what the server can handle, but because the database quietly filled up with data nobody’s actively using.
Checkout is usually where it shows up first. It’s the page in the whole store that queries the most tables at
once — cart contents, shipping options, payment gateways, tax calculations — so any database bloat has the most
places to slow things down.
What's actually accumulating #
- Abandoned cart sessions — every incomplete checkout leaves rows behind indefinitely by default
- Post revisions — WordPress saves a new revision every time a product or page is edited, with no automatic limit
- Expired transients — temporary cached data that often never gets cleared once it expires
- Orphaned order items and meta — left behind by deleted or refunded orders
What to clean, and how often #
- Clear abandoned cart sessions older than a set window — weekly is usually enough.
- Limit post revisions at the WordPress configuration level, then clean out the historical backlog once.
- Purge expired transients — a quick, low-risk cleanup that often reclaims meaningful table size.
- Clean orphaned order meta left behind by refunded or deleted orders, on a monthly cadence.
The slowest query on your checkout page is rarely the one anyone wrote on purpose.
Adlux growth team
Measuring the impact properly #
Database size alone isn’t the metric that matters — query time on the actual checkout page is. Before and after
any cleanup, a server-side timing check on checkout page load gives a real read on whether the work moved the
number that affects customers.
Frequently asked questions #
Yes, with a backup taken first and cleanup scoped to genuinely stale data — expired transients, old abandoned carts, revision backlogs. Live order and customer data should never be touched by a routine cleanup.
It varies by how bloated the database has become, but checkout page load improvements of 20-40% are common on stores that haven’t been cleaned in over a year.
No — hosting and database hygiene solve different problems. A bloated database will slow down even excellent hosting, and good hosting can’t fully compensate for years of accumulated cruft.
The takeaway #
Checkout speed is one of the quietest conversion levers in eCommerce, and database bloat is one of the quietest
causes of checkout slowdown. A scheduled cleanup — not a one-time fix — is what keeps the two from ever meeting.
Written by the Adlux team from live account work. If you want this thinking applied to your store, the audit is free and the findings come in writing.