Caching and page speedPro
10Web Booster MCP: what GoBuildWP can and cannot reach
A 10Web Booster MCP connection is the thinnest of GoBuildWP's cache integrations. Booster is SaaS-backed: its optimisation settings are held by 10Web, and its cache-clearing method is an instance method with no public accessor, so GoBuildWP declares no purge entry point for it. What remains is detection, reading and writing the local tenweb_ and twoptimize_ rows, and measuring what visitors are actually sent.
tenweb_booster- Layer
- page
- Declared purge scopes
- No purge entry point declared
- Shared keys
- None
- Detected by
- plugin folder tenweb-speed-optimizer
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.
Data model
A local plugin fronting a remote optimiser
Booster requires signing up to the 10Web service, and its free plan covers the homepage plus five inner pages, per the WordPress.org listing. Page caching, minification, deferral, critical CSS, WebP, lazy loading and font swapping are driven from 10Web, and on 10Web's own hosting an NGINX FastCGI cache is added in front.
Inside WordPress, GoBuildWP claims options whose names begin with tenweb_ or twoptimize_, and that is everything the driver can see. With the settings that matter held remotely, editing one of those rows is unlikely to change how pages are optimised; GoBuildWP's note for the driver says as much.
Clearing is the gap. GoBuildWP's purge map records that Booster's clear_cache lives on an object with no public way to reach it. A vendor reply on the WordPress.org support forum mentions a two_clear_cache hook, but it is not in formal documentation and GoBuildWP does not call it.
Option name prefixes
tenweb_twoptimize_
SaaS-backed optimisation, so the settings that matter are held remotely; only its local option rows are readable and writable here.
Limits
What 10Web keeps to itself
- No purge entry point at any scope, including GoBuildWP's automatic purge after its own writes; the result for this layer always says so.
- Optimisation settings and page coverage are held by the 10Web service.
- The tenweb_ prefix is the boundary GoBuildWP enforces: any row whose name starts with it or with twoptimize_ is treated as Booster's.
- Native row writes can be reversed with rollback-change, but that restores the local row only.
Questions
10Web Booster questions
Can the agent clear 10Web Booster's cache?
No. GoBuildWP found no public entry point to call, so it reports Booster as not purged rather than pretending. Clear it from 10Web's controls.
Why doesn't GoBuildWP use the two_clear_cache hook?
It appears in a support-forum reply rather than in formal documentation, and GoBuildWP's purge map only carries entry points it can defend.
Can an AI agent change which pages Booster optimises?
No. Coverage depends on your 10Web plan and is managed there; the free plan covers the homepage and five inner pages.
Worked example
Inspect inner-page delivery and check Booster in 10Web
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
The user gets delivery evidence for one page. GoBuildWP cannot see which pages the plan includes or clear Booster's cache, and delivery diagnostics do not prove Booster coverage. Check page inclusion and completion in 10Web’s dashboard.
Inspect delivery through GoBuildWP and manage optimization in 10Web. No purge declared here does not establish that the vendor has no other API.
Is 10Web Booster actually optimising /services/? It feels slow.
wppilot/cache-check-setupReadLists tenweb_booster and any other layer, and states that no purge is available for Booster.
wppilot/cache-measure-pageReadReports time to first byte across runs, HTML weight, render-blocking stylesheets and head scripts, and images without dimensions on /services/.
wppilot/cache-verify-in-browserReadReturns browser checks for that URL and the PageSpeed report links for both form factors.
A suggested sequence from the ability reference, not a recorded run.
Abilities
What the cache abilities do with 10Web Booster
| Ability | What it does here | Undo and limits |
|---|---|---|
cache-check-setup | Lists tenweb_booster as a page layer from the tenweb-speed-optimizer folder, every purge scope false, with the SaaS reason attached. | It cannot tell you which pages your 10Web plan covers. |
cache-purgecache-warm | Every purge result marks Booster as not purged while other layers on the site are still purged. Warming requests pages, which Booster may or may not answer from its cache. | Booster's cache has to be cleared from 10Web's own controls. |
cache-get-settingscache-set-native | List the tenweb_ and twoptimize_ rows and change one by exact name, confirm=true each time. | A changed local row does not reconfigure the 10Web service. |
cache-set-settingscache-apply-presetcache-list-presets | Come back unsupported for every key; there is nothing canonical to set. | Booster's optimisation levels are chosen in 10Web, not here. |
cache-list-actionscache-run-action | Find no action for this driver. | Nothing to run. |
cache-begin-experimentcache-revert-experimentrollback-change | Capture and restore the local rows under both prefixes. | The remote configuration is not part of any snapshot. |
cache-measure-pagecache-verify-in-browser | The most useful pair on a Booster site: server-side delivery numbers for a URL, then browser checks for damage from deferral or critical CSS, with PageSpeed report links. | A page your plan does not cover will not reflect Booster's work, and GoBuildWP cannot tell covered from uncovered pages. |
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.
Other plugins
Booster alongside other optimisers
- The vendor says using another speed optimiser alongside 10Web Booster is not recommended. If check-setup finds a second optimiser, raise that overlap before tuning anything.
- On 10Web hosting a FastCGI cache sits in front of WordPress. check-setup lists the host and edge layers it recognises under edge_layers, and cache-purge does not reach any of them.
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.
10Web Booster is a separate product; no partnership or endorsement is implied.