litespeed/get-autoload-summary reports the size and count of autoloaded options: the data WordPress loads on every single request, before anything else happens.
A large autoload total is one of the most common causes of a site that is slow everywhere at once, and it is invisible from the front end.
At a glance
| Ability | litespeed/get-autoload-summary |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Database Health |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Autoloaded options are fetched in one query at the start of every request and unserialised into memory. That happens on the front page, on an admin screen, on a REST call, on every AJAX request a plugin makes.
So when the total grows — a plugin caching data in an option, a log accumulating, a settings blob that was never cleaned up after the plugin was removed — the cost lands on everything equally. There is no slow page to investigate; the site is just uniformly worse.
A few hundred kilobytes is common and fine. Several megabytes is a real problem and is usually one or two options rather than many.
This ability reports. Changing options is the job of the options abilities, and removing the wrong autoloaded option breaks a plugin, so the sequence is: measure here, identify the culprit, then act deliberately.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
total_bytes | integer | How much autoloaded data is loaded on every request. |
count | integer | How many autoloaded options there are. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Why is this site slow on every page?
It resolves to one call:
{
"ability": "litespeed/get-autoload-summary",
"parameters": {}
}Worth knowing
- Autoloaded data is loaded on every request, including AJAX and REST.
- A few hundred kilobytes is normal; megabytes is not.
- The cost is usually one or two options, not many small ones.
- Read-only. Removing an autoloaded option a plugin needs breaks it.
Related abilities
- Get Database Cleanup Summary — the other database weight
- Get Environment Report — the wider picture
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category