Caching and page speedPro
What GoBuildWP can read on an Aruba HiSpeed Cache site
GoBuildWP detects Aruba HiSpeed Cache and can read or write its named option rows. It cannot empty the server-side cache. Aruba's cache lives on Aruba's servers, and the plugin exposes only nonce-checked admin handlers, so GoBuildWP declares no purge entry point rather than guess one. Here is what an agent can usefully do on an Aruba site, and where a person still has to click.
aruba_hispeed- Layer
- page
- Declared purge scopes
- No purge entry point declared
- Shared keys
- None
- Detected by
- plugin folder aruba-hispeed-cache
Installed class, method or listener checks and per-layer results determine whether a purge ran. Neither a declaration nor a returned ran flag proves public freshness.
- Edition
- Pro
- Abilities
- 16
- Requires
- WordPress 6.9+, PHP 8.0+
Before changing cache settings, inspect captured drivers and not_captured. After reverting, inspect restored, deleted, not_restored, verified and purged_layers. Use a separate cache-purge result when you need details for each layer. Storage verification checks captured values; it does not establish functional recovery or public freshness. Revert may overwrite later settings, and vendor configuration regeneration or a re-save can still be required.
Check each measurement run’s fetched_via before treating it as public-path evidence. cache-verify-in-browser supplies checks and does not operate a browser. Automatic purge coalesces targets within the request and runs on shutdown; it is not necessarily one immediate flush per call. Verify generated files, object/page/edge caches and actual visitor behavior separately.
Limits
Read this first: what an agent cannot do with HiSpeed Cache
- No purge at any scope. Every GoBuildWP purge, including the automatic one after its own writes, skips this layer and says so in the result.
- The service is switched on in Aruba's hosting panel. Flipping an option row does not provision it.
- Cart, checkout and login pages are excluded by the service automatically, per Aruba's documentation, and no GoBuildWP setting changes that list.
- Row writes are undoable with rollback-change; pages already held in Aruba's memory are not part of any undo.
Data model
A plugin that steers a cache on Aruba's servers
HiSpeed Cache is part of Aruba hosting. The plugin is a control surface for a server-side cache that keeps dynamic content in server memory, with automatic and manual purging and preloading. Aruba's guide says the service must be enabled in the hosting panel and can take up to 15 minutes to become active; on any other host the plugin installs but does nothing.
Cached pages therefore live on Aruba's infrastructure, not in wp-content, and the plugin's local state is a handful of option rows. GoBuildWP treats names beginning with ahsc_ or aruba_hispeed as the plugin's and nothing else; those rows can be listed in full and changed one exact name at a time.
The comment beside Aruba's empty entry in GoBuildWP's purge map explains the gap: the plugin's purge controls are AJAX and admin-bar handlers that read request state and check nonces. None of them can be invoked from an ability, so the driver was deliberately left without a purge.
Option name prefixes
ahsc_aruba_hispeed
Host-specific cache with no documented settings API, so nothing is mapped. Its option rows are readable and writable by name.
Abilities
Each cache ability on an Aruba-hosted site
| Ability | What it does here | Undo and limits |
|---|---|---|
cache-check-setup | Lists aruba_hispeed as a page layer whenever the aruba-hispeed-cache folder is active, with the all, url and post purge scopes all false. | It reports the plugin, not Aruba's service. On a non-Aruba host the layer still appears although nothing is being cached by it. |
cache-purgecache-warm | cache-purge marks this layer as not purged, with the reason, while still purging every other layer it found. cache-warm fetches pages, which helps those other layers. | Whether Aruba's cache answered a warm request is invisible to GoBuildWP. The vendor's Delete cache button, which empties the whole site, is the only manual purge. |
cache-get-settingscache-set-native | List the rows under ahsc_ and aruba_hispeed; change one after the ability has read it back, with confirm=true. | The native write's usual follow-up purge has nothing to call here, so a changed row does not clear anything already cached on Aruba's servers. |
cache-set-settingscache-apply-presetcache-list-presets | Report every key unsupported, since Aruba publishes no settings API that GoBuildWP could map. | Unsupported is a statement of reach here, not an error. |
cache-list-actionscache-run-action | Find no Aruba action. Preloading is run by the hosting service itself. | There is nothing to queue and nothing to refuse. |
cache-begin-experimentcache-revert-experimentrollback-change | Snapshot and single-change undo both cover the ahsc_ and aruba_hispeed rows. | Restoring a row leaves copies built under the old setting on Aruba's side; press Delete cache after any revert. |
cache-measure-pagecache-verify-in-browser | Repeated fetches show whether responses are quick and stable, and the browser checks cover optimisation damage in the delivered page. | The HIT or MISS headers measure-page recognises are generic ones; none is specific to Aruba, so a reported hit does not prove Aruba's layer answered. |
Reference: /docs/reference/cache
Shared cache module; do not add this count across drivers. Edition and effect labels describe the source catalogue. The installed schema, dependency versions, licence, WordPress capability, safety profile and per-ability policy determine availability; labels alone do not prove confirmation or recovery.
Worked example
Get a price change past Aruba's cache
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
Everything GoBuildWP can reach is purged, and the agent reports that Aruba's copy is outside its reach. Aruba documents an automatic purge when content is updated, so the edit may already have cleared it; if the old prices persist, the Delete cache button in the plugin does the rest.
The current GoBuildWP driver declares no supported Aruba purge. Use the plugin’s Delete cache control when needed, then fetch or inspect actual expected prices; cache-measure-page does not return page HTML. Check remaining origin, host, CDN and browser layers if output stays stale.
I've updated the prices on the pricing page. Make sure visitors actually see them.
wppilot/cache-check-setupReadLists aruba_hispeed with every purge scope false, plus any other layer on the site with its own scopes.
wppilot/cache-purgeWriteScope post with the page id. Other layers are purged; the Aruba result says no purge entry point is available for it.
wppilot/cache-measure-pageReadFetches the pricing page and returns its headers and timings, without returning HTML. Inspect the actual page content separately against the expected prices.
A suggested sequence from the ability reference, not a recorded run.
Questions
Aruba HiSpeed Cache questions
Why won't the AI agent clear my Aruba cache?
Aruba HiSpeed Cache offers no function or hook an outside caller can use; its clear buttons are admin handlers protected by nonces. GoBuildWP reports that plainly instead of calling something that would only appear to work.
Does Aruba HiSpeed Cache do anything on another host?
Its WordPress.org page says it works only on Aruba hosting. GoBuildWP will still detect the plugin elsewhere, so check where the site is hosted before reading anything into that layer.
Can GoBuildWP switch the HiSpeed service on for me?
No. The service is enabled from Aruba's hosting control panel and can take up to 15 minutes to become active.
My edit shows in the editor but not on the site. Which cache is holding it?
Run cache-check-setup, then cache-purge. If every other layer reports purged and the page is still old, likely places to look next are Aruba's host-level cache and any edge in front of it, which check-setup lists under edge_layers. Browser caching, a layer check-setup did not detect, or content that was not actually saved can produce the same symptom.
Where these facts come from
GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.
Aruba HiSpeed Cache is a separate product; no partnership or endorsement is implied.