litespeed/update-html-settings changes HTML handling: minification, DNS prefetch and preconnect, and the removal toggles for query strings, emoji scripts and noscript tags.
This is the safest part of the optimisation pipeline, with two exceptions worth knowing.
At a glance
| Ability | litespeed/update-html-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › CSS, JS & HTML |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
HTML minification strips whitespace and comments from the rendered page. It is safe almost everywhere, and the almost is inline JavaScript and CSS with comments that depend on line breaks — rare, but a real failure when it happens.
DNS prefetch and preconnect are pure wins when pointed at hosts the page actually uses, and mildly wasteful when pointed at hosts it does not. Preconnect in particular opens a connection; a list of ten preconnects to hosts that are never contacted costs the visitor ten connections.
Removing query strings from asset URLs is the first exception. It improves caching on some proxies and it removes the version marker that makes a browser fetch a changed file — so after a theme update, visitors can hold a stale stylesheet indefinitely.
Removing emoji scripts is genuinely free on most sites. Removing noscript tags is the second exception: it is only free if nothing on the site relies on them, and lazy-loading fallbacks sometimes do.
The write is a patch, not a replacement. Send one key and one key changes; everything else in the area is left alone. The response names the keys that actually moved, so a payload that matched the existing values comes back with an empty list rather than a misleading success.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
settings | object | Yes | A map of setting key to new value. Keys outside this area are refused, and the refusal lists what the area accepts. |
What comes back
| Name | Type | What it is |
|---|---|---|
updated | array | The keys that actually changed. An empty array means every value you sent was already set. |
settings | array | Every setting in the area after the write, in the read shape. |
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:
Strip the emoji scripts and minify the HTML.
It resolves to one call:
{
"ability": "litespeed/update-html-settings",
"parameters": {
"settings": { "optm-html_min": true, "optm-emoji_rm": true }
}
}Worth knowing
- Removing asset query strings removes the cache-busting marker. Browsers can hold stale files after an update.
- Preconnect to hosts the page does not use costs the visitor connections.
- Noscript removal is only free if nothing relies on noscript fallbacks.
- Generally the safest area here.
Related abilities
- Update CSS Settings — the riskier neighbour
- Get Optimisation Settings — read the whole pipeline
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category