We optimise your multisite network’s shared database tables — which grow larger and more complex than a single-site installation’s, since they hold data for every subsite together — cleaning up inefficiencies and improving query performance across the whole network rather than just one site’s portion of it.
Network database optimization
The network's shared database tables optimised, without touching any individual subsite's own data.
- 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 sufficient to review and optimise network tables
- Confirmation of your network’s approximate size (number of subsites, rough content volume)
- Confirmation of a maintenance window, given the scope of database-level work across a shared structure
This or something else?
| You want your multisite network’s shared database tables optimised for performance | This fix covers it |
| You want a specific subsite’s own performance issue diagnosed, not the shared network tables | Meta query performance optimization, in the Integrations & Automation bucket, if the issue is subsite-specific |
| You want general database cleanup, not specifically multisite’s shared structure | Database & Data Hygiene category fixes for a standard, single-site database |
| You’re experiencing a specific, known slow query across the network | Worth describing the specific query or symptom directly for a more targeted diagnosis |
What we do
- Review the network’s shared database tables for inefficiencies
- Identify accumulated cruft (orphaned data, excessive revisions) across the shared structure
- Optimise indexing and clean up genuinely safe-to-remove accumulated data
- Verify performance improvement across a representative sample of network activity
- Test that no subsite’s data or function was affected by the optimisation
- Provide a written summary of what was optimised
What is included
- Multisite shared database tables optimised
- Safe cleanup of accumulated cruft across the network structure
- Verified performance improvement
- A written summary of the optimisation
Not included
- Subsite-specific performance issues unrelated to the shared network tables — a separate, related fix if that’s the actual concern
- General single-site database cleanup, a different scope entirely
- Ongoing database maintenance as a standing service
- Hosting-level upgrades if the network has genuinely outgrown its current resources
Questions about this fix
Why would a multisite network's database need different optimisation than a single site?
Multisite's shared tables hold data across every subsite together, so inefficiencies compound differently and at greater scale than a single-site installation's own, smaller tables — the optimisation approach accounts for that shared structure specifically.
Will this affect any individual subsite's content or settings?
We verify specifically that no subsite's own data or function is affected — this optimises the shared, underlying structure without altering what any individual subsite actually contains or does.
How do I know if my network's database genuinely needs this?
Slowing admin performance across the network generally, or specific queries taking longer as the network has grown, are reasonable signs worth investigating — we can also assess this directly if you're unsure.
Is this riskier than optimising a single-site database?
There's more at stake given the shared structure affects every subsite simultaneously, which is exactly why we recommend a maintenance window and verify thoroughly afterward rather than treating this as routine, low-stakes cleanup.
How often should this be done for a growing network?
There's no fixed schedule, though a network adding subsites and content steadily would reasonably benefit from periodic review as it continues to grow, rather than only addressing it once performance becomes a noticeable problem.
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.