KakapoWP KakapoWP
Log in Try for free
Kakapo Performance

Autoload

These rows don't cost time once — they cost it every time.

WordPress fetches every option flagged autoload in a single query — on every page view, every image, every REST call. For each of those rows, Kakapo works out the actual byte count in PHP. Next to it, you see which name belongs to which plugin or theme. Take an option out and only its autoload column changes — the value itself stays fully intact.

Autoload

Byte count per autoloaded option · the flag goes, the value stays

ActiveMeasure again

What Autoload offers

Bytes per option counted in PHP, not estimated
The 25 largest autoloaded options as a table
Mapped to plugin, theme or core by name
The same warning threshold as the WordPress site health report
Nothing is deleted, only the flag is removed
Every change can be undone one by one or all at once

Here's how it works

1

Measure autoloaded options

2

Read the origin per row

3

Remove the flag, the value stays

FAQ about autoload

What exactly changes about an option?
Their flag, nothing else. The content stays intact byte for byte; whoever reads it still gets it — WordPress then fetches it with a single query. That is also the worst case if the assignment is off: one query more, no data loss. You can take back every change individually or all at once.
Why are the biggest rows so often locked?
Off limits is everything belonging to the WordPress core, to an active plugin or to the active theme. What a running plugin reads on every request is known only to that plugin, and comparing names is no basis for it. Also not available for selection are transients — those belong in the deep cleanup — and everything under 1 KB, where the extra individual query costs more than the bytes saved.
Can I read off the savings in seconds?
Not here, and this section does not fake a figure either. It names bytes: how many go over the database connection on every request and how many of them you take out. What that turns into in terms of time depends on your database, on the object cache and on your host.

More performance features

Ready?

Try Performance free for 24 hours.

No credit card, no risk. Up and running in 2 minutes.

Try it for free now