Complaint 15 of 43
Database and autoload bloat
At around 3MB of settings loaded on every request, one host reports slow admin screens, checkout failures during sales and 502 errors.
The short answer: Each Hostless Duck module keeps its data in its own tables and a Database Cleanup module is live; we have not measured Hostless Duck on very large, old sites.
The figures
- around 3MB
of settings loaded on every request is where one host reports slow admin screens, checkout failures during sales and 502 errors
Kinsta - over 2 MB
of autoloaded settings is "almost certainly your problem" in a second guide's table
TalosWP
Each figure was read at its source on 21 November 2026. They are other people's measurements, not ours.
The pain
Settings that load on every request pile up. One host puts the trouble line near 3MB: slow admin screens, checkout failures during sales and 502 errors.
Who feels it most: Shops and old sites.
Why it happens
- WordPress keeps settings in one shared table and loads every setting marked "autoload" into memory at the start of every request. Source: Kinsta
- When a plugin saves a setting, autoload is switched on unless the plugin's author says otherwise, and nobody cleans up afterwards. Source: TalosWP
- Switching a plugin off does not delete its data, and uninstalling it often does not either. The usual culprits are settings left by plugins that are long gone and temporary cache entries. Source: TalosWP
- The guides do not agree on one danger line. The same host says anything above 1MB should be looked into, and a second guide calls anything over 2 MB "almost certainly your problem". Source: Kinsta
What it costs
- The weight is paid on every page and every admin screen, by every visitor, whether or not the page needs those settings. Source: Kinsta
- The failures land where money changes hands: the host names checkout failures during sales. Source: Kinsta
- Cleaning it up is database work. One guide gives an example of a clean-up that took more than a second off admin page loads. Source: TalosWP
How Hostless Duck is built differently
Each module keeps its data in its own tables, and a Database Cleanup module is live. We have not measured Hostless Duck on very large, old sites.
The live module: Database Clean-up.
Using a plugin for this today? See what carries over from WP-Optimize, Advanced Database Cleaner or WP-Sweep.
Sources
| Source | What kind | Last read |
|---|---|---|
| Kinsta: "Key WordPress database tables for maintenance agencies" | Secondary: a vendor or a competitor | 21 November 2026 |
| TalosWP: "Why your WordPress admin got slow, and why it is probably autoload" | Secondary: a vendor or a competitor | 21 November 2026 |
Found a link that no longer says what we say it does? That is a fault in this page, and we would rather fix it than defend it.
The other articles
Does your site have this one?
Give us your site's address and we read its public pages once: its theme, its plugins, and what Hostless Duck has for each. A real scan of your public pages, never a made-up result. No card.

