litespeed/get-media-status reports whether lazy loading is active for images and iframes, what placeholder is in use, and how many exclusions are configured.
It is the diagnostic when images do not appear.
At a glance
| Ability | litespeed/get-media-status |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Images & Lazy Load |
| 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
The usual cause of missing images on a LiteSpeed site is lazy loading combined with a theme that moves images with JavaScript. LiteSpeed replaces the image source with a placeholder and stores the real one in a data attribute; its own script swaps them back when the image scrolls into view.
A theme or slider that clones, moves or re-renders the image element after that point breaks the connection. The element still exists, the real source is still in an attribute, and nothing ever swaps it in.
The symptom is an image that never loads, or loads only after an unrelated interaction. The fix is to exclude that image — by source, by class, or by parent class — rather than to disable lazy loading everywhere.
The exclusion count in the response is a useful signal by itself: a site with many exclusions has a theme that fights lazy loading, and turning it off for that theme may be simpler than maintaining the list.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
images | object | Whether image lazy loading is active. |
iframes | object | Whether iframe lazy loading is active. |
placeholder | string | The placeholder in use. |
exclusions | object | How many exclusions are configured, by list. |
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:
Some images on the homepage never load — what is going on?
It resolves to one call:
{
"ability": "litespeed/get-media-status",
"parameters": {}
}Worth knowing
- Missing images are usually lazy loading plus a theme that moves elements with JavaScript.
- Exclude the image rather than disabling lazy loading site-wide.
- A large exclusion count suggests the theme and lazy loading do not get on.
Related abilities
- Update Media Exclusions — exclude the offending images
- Update Lazy Load Settings — change the behaviour
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category