built with claude referral only running on claude + openclaw
← BACK TO THE BLOG

// BLOG

WHY YOUR WORDPRESS SITE IS SLOW EVEN WITH GOOD HOSTING

wp_options → autoload=yes on every row → loaded on every single request

THE PART NOBODY CHECKS

A client moves to better hosting, installs a caching plugin, does everything right, and the site is still sluggish. Not broken, not throwing errors, just heavier than it should be. Nine times out of ten when I dig in, the front end and the theme are fine. The problem is sitting in the database, in a table almost nobody looks at directly: wp_options, and specifically the rows in it marked to autoload.

What "autoload" actually means

Every WordPress install stores settings, one-off values, and cached data as rows in wp_options. Some of those rows are flagged autoload = 'yes', which tells WordPress to pull them into memory on every single page load, whether that particular page needs them or not. It's meant for small, frequently-needed values: the site's active theme, permalink structure, a handful of plugin settings. On a healthy site, total autoloaded data adds up to well under a megabyte or two.

The problem is that plugins don't always clean up after themselves. A plugin that stores a large settings array, a page builder that caches generated CSS in an option, a transient that was set to autoload and never properly expires, leftover data from a plugin you deactivated two years ago, none of it disappears on its own. It just sits there, marked autoload, getting pulled into memory on every request forever. I've seen sites where autoloaded data alone was pushing 40 to 80 megabytes. That's not an edge case; that's what several years of plugin churn on an actively maintained site looks like if nobody ever checks it.

Why caching doesn't save you here

Page caching works by skipping PHP entirely for logged-out visitors hitting a page that's already been generated. That's real, and it helps. But it doesn't touch anything that still has to run PHP: wp-admin for every logged-in user, cron jobs, REST API calls, AJAX requests, WooCommerce cart and checkout pages, any logged-in membership content, search. All of those still load the full autoloaded dataset on every single hit. A site can have a perfect caching setup on excellent hosting and still feel heavy in the admin, slow at checkout, and sluggish for logged-in users, because the part of the site that caching can't reach is the part carrying the weight.

How to actually check it

If you have WP-CLI access (most decent hosts give you this through SSH), the fastest check is one line:

wp option list --autoload=on --format=table

That lists every autoloaded option with its size, sorted so the worst offenders are easy to spot. If you don't have shell access, the free Query Monitor plugin reports total autoloaded data size right on the page, under its Database panel, no command line required. Either way, the number you're looking for is a total. Under a megabyte or two is normal. Tens of megabytes means something's been left behind.

Fixing it without breaking anything

This is the part where I'd normally point you at a tool, and I looked hard for a way to build one. The honest answer is that a website-based tool can't do this safely: it needs direct database access, and handing that to a browser-based tool is a bigger risk than the slowdown it's fixing. What actually works is boring and manual: back up the database first, always, a habit that's saved me more than once and one of the lessons I learned the hard way. Then look at what Query Monitor or WP-CLI flagged as large, check whether the plugin that created it is still installed and active, and if it's leftover data from something removed years ago, it's usually safe to delete. Expired transients specifically are almost always safe to clear; a plugin like WP-Optimize or WP-Sweep can do that part automatically. Anything tied to a plugin you're still actively using is worth leaving alone unless you know exactly what it does.

This is written from checking exactly this on client sites, not a general guide copied from somewhere else. Every install is different; back up before you touch anything in the database directly.

Not sure if this is what's slowing your site down, or found something in Query Monitor you're not sure is safe to delete? Ask it here, for free. If you'd rather have someone check it directly, that's the work I take on by referral.

GET IN TOUCH →