Scan a website for speed problems with OpenClaw

Scanning site speed with OpenClaw means letting the always-on agent run an xSpeed Scan on a schedule of your own, then report the grades, so you check results and do not start the scans.

list_sitesget_speed_scanrun_speed_scan

Last updated: October 2026

Example session · OpenClaw

You: Set up a weekly xSpeed Scan MCP check on rival-one.com. Run it once now so I can see the format.

run_speed_scan(url: rival-one.com, strategy: both) read-only scan mcp
→ Desktop grade B, mobile grade C. Report link included.

OpenClaw: This week: desktop B, mobile C, and the report link is above. Weekly job saved for Monday. It will scan rival-one.com, compare the grades with the last run and message you only the changes. This first run is the baseline.

You: Add rival-two.com, but wait a few minutes between the two scans.

OpenClaw: Done. The job scans one site, pauses, then scans the next, so it stays under the limit of four scans per ten minutes.

How OpenClaw handles this

OpenClaw runs all the time and can run automations, which is the one thing the Hub does not do for you: the Hub has no scheduler for agent prompts. So the weekly check on a competitor's site is an OpenClaw job. Once a week it calls run_speed_scan through the no-account Scan MCP on each URL, reads the grades and the top failing check, and sends you a short message. Nothing on the competitor's site is touched, since the Scan MCP is read-only.

For your own sites in xSpeed Hub, give the job the Hub and have it start with get_speed_scan, which reads the scan history for free. It only needs run_speed_scan when the latest report is old, and the message then says what moved since the last one. Use a fresh scan only when you changed something, since the same URL within ten minutes returns the existing report.

Space the jobs out. The Scan MCP allows four scans per caller per ten minutes, so a Monday job covering nine sites will hit the limit and stop partway unless it works in batches with a pause between them. Tell the job to name the report link for each site in its message, so you can open the evidence behind any grade that looks off.

Set up OpenClaw once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the OpenClaw guide.

1Put your sites in xSpeed Hub

Sign in at app.xspeedcache.com with Google or email; the Hub is free and has no site cap. Then connect each WordPress site from its own dashboard: click Connect Hub in the xSpeed Cache top bar, then Connect via xSpeed Hub. Each site needs the free xSpeed Cache plugin.

2Save xSpeed Hub as an MCP server

Run this on the machine that hosts your OpenClaw Gateway. Set the transport to streamable-http: OpenClaw falls back to SSE when you leave it out. With --auth oauth the command saves the server without a connection test, because sign-in has to happen first.

Terminal

openclaw mcp add xspeedhub \
  --url https://app.xspeedcache.com/xspeed/mcp \
  --transport streamable-http \
  --auth oauth

3Sign in with openclaw mcp login

OpenClaw prints an authorization URL and listens on a loopback address for the callback. Open the URL, sign in to xSpeed Hub and approve; the token exchange finishes by itself. There is no token to paste. If your browser is on another machine, copy the code from the redirect and pass it back with openclaw mcp login xspeedhub --code. Then check the connection.

Terminal

openclaw mcp login xspeedhub
openclaw mcp doctor xspeedhub --probe

4Add the xSpeed Scan MCP for sites you do not run

Prompts that scan a public URL use the xSpeed Scan MCP, a separate server from the Hub. Add it to OpenClaw the same way as the Hub above, as a second server (xspeedscan, for example) with the URL https://xspeedcache.com/scan/mcp, and leave out any sign-in setting, such as an OAuth or auth option or an Authorization header, because the Scan MCP needs no account, token or sign-in. On a plan that allows one custom connector, add whichever server the prompts you use need.

Text

https://xspeedcache.com/scan/mcp

1 / 4

Full OpenClaw setup, sign-in options and FAQ

Before you send a prompt that changes something

Reads change nothing on your sites, though contact_support emails xSpeed support. Writes run once your connection allows them, so your client's approval prompt and a read-only connection (the token's Read-only everywhere switch, or a Viewer sign-in) are the gates that matter. OpenClaw gives you two client-side gates, and the Hub adds none. First, openclaw mcp tools xspeedhub --include limits which tools exist for the agent, so a list of read tools keeps every write out of reach. Second, when the Codex runtime runs your agent turns, MCP tool approvals follow the session's permission posture, and the default full-permission posture does not prompt. openclaw mcp configure xspeedhub --approval prompt asks on every call, and Allow Always saves a grant for that one tool with any arguments. OpenClaw's docs describe that per-call prompt for the Codex runtime; with its own embedded runtime, use the tool filter to decide what the agent can call. The Hub has no confirmation step of its own.

What do I ask?

Three prompts written for OpenClaw. More for this job are below.

Prompt for OpenClaw

Every Monday, use the xSpeed Scan MCP to scan these three competitor URLs in separate batches, and message me the desktop and mobile grades.

Prompt for OpenClaw

Each morning, use xSpeed Hub to read the scan history for my client sites and tell me only if a grade dropped.

Prompt for OpenClaw

Once a week, ask xSpeed Hub for a mobile-only scan of my site and keep a running list of the grades.

What happens, step by step

An xSpeed Scan grades a site from 0 to 100 using server probes (time to first byte, compression, cache evidence, redirects, platform detection) plus a Lighthouse run, and names the fix for every failing check. An agent can start one two ways. Through xSpeed Hub, run_speed_scan scans a site you have connected. Through the no-account Scan MCP at https://xspeedcache.com/scan/mcp, it scans any public URL and cannot change anything. Either way you get a report link to share.

Check what the site already scored

get_speed_scan without a scan id returns the site's scan history, newest first, plus a summary of the latest report. It starts nothing and spends nothing, so the Hub tells the agent to read it first when you ask what a site scored.

Start a scan

run_speed_scan runs the full scan on a site you connected to the Hub. strategy is both (the default), desktop or mobile; one device alone costs half the engine's quota. The scan takes 20 to 60 seconds. The Hub waits about 50 seconds and, if the scan is still running, hands back a scan id.

Poll if it is still running

Call get_speed_scan with scan_id. While the scan runs it returns the running status and a note to ask again in about 20 seconds. The report page is live from the start and refreshes itself.

Read the result

The summary carries the grade, the four dimension scores, what was measured and the top fixes ranked by points recoverable, each with the xSpeed feature that fixes it. The headline grade is the desktop run. The mobile run is graded alongside it, so the agent should mention both when they differ.

Scan a site you do not run

For any other public URL, the agent uses the Scan MCP at https://xspeedcache.com/scan/mcp. There is no account and no sign-in. It takes a url, returns the same graded report and a link at xspeedcache.com/scan/r/<id>, and is limited to 4 scans per caller per 10 minutes.

Fix, wait, re-scan

After a change, wait several minutes and scan again with fresh: true. Without it, the scan service reuses any report from the last 10 minutes and the agent will show you the old number.

Reference

Hub route	run_speed_scan, then get_speed_scan with scan_id; only for sites connected to your Hub
Scan MCP route	https://xspeedcache.com/scan/mcp, no account, 5 tools, read-only, any public URL
Scan MCP limit	4 scans per caller per 10 minutes
Why run_speed_scan is a write	It spends a shared scan allowance and stores a report; it changes nothing on the site
Read-only Hub connection	run_speed_scan is refused; get_speed_scan still works. Applies to the connection token with Read-only everywhere on and to a Viewer sign-in; an OAuth sign-in gets the scopes the client asks for
Duration	20 to 60 seconds; the Hub waits about 50 seconds, then returns a scan id
Poll argument	scan_id on the Hub tool, scanId on the Scan MCP tool
strategy	both (default), desktop or mobile; one device costs half the quota and becomes the headline
fresh	true forces a new measurement; otherwise a report from the last 10 minutes is reused
Report link	xspeedcache.com/scan/r/<id>; add .md for a Markdown twin an agent can read
Report visibility	Hub scans are filed unlisted; Scan MCP scans are public in the scan directory by default

Rules worth keeping

Read before you spend. Ask for the scan history first; start a new scan only when you want a fresh measurement or something changed.
A report link is not private. An unlisted report is kept out of the scan directory and search, but anyone with the URL can open it. A scan started through the Scan MCP is public by default.
run_speed_scan changes nothing on your site, but the Hub classes it a write, so a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) refuses it and your client may prompt for it. Use get_speed_scan, or the Scan MCP for a public URL, when you want a strictly read-only route.
Compare like with like. A scan that lost its Lighthouse run is marked partial and is not comparable with a full one, and the lab grade is not the same as real-visitor Core Web Vitals, which the report shows separately.
A scan cannot reach private, local or password-protected sites, and a site behind a bot challenge returns a report that says its server checks were not measured.

Good to know with OpenClaw

An unattended job needs the right connection. A read-only Hub connection (the connection token with Read-only everywhere on, or a Viewer sign-in) refuses run_speed_scan, because the Hub classes it as a write tool that spends the shared speed-test allowance, so a Hub job that must start scans needs a connection that allows writes, and you should give it a plain budget in the prompt. An automation runs unattended, so nobody is there to answer a prompt, and OpenClaw's default full-permission posture does not prompt at all. A tool filter that includes only get_speed_scan keeps run_speed_scan out of reach. History reads with get_speed_scan stay allowed on a read-only connection, so a report-only job can use that. Scan reports are public by default, so a job that scans competitors leaves a report anyone with the link can open.

More prompts for this job

Prompts about your own sites work in any client connected to xSpeed Hub. A prompt that scans a site you do not run, or names the scan server, needs the xSpeed Scan MCP from the setup above.

Prompt

Using xSpeed Hub, what did the shop site score on its last speed scan? Do not start a new one.

Prompt

Use xSpeed Hub to run a speed scan on blog and give me the three fixes that recover the most points, plus the report link.

Prompt

With xSpeed Hub, scan only the mobile view of shop and tell me the grade.

Prompt

I changed the theme this morning. Use xSpeed Hub to run a fresh scan on docs and compare it with the previous report.

Prompt

Use the xSpeed Scan MCP to grade [competitor URL] and tell me what its biggest weaknesses are.

Prompt

The speed scan on shop is still running. Ask xSpeed Hub to check it again and tell me when it finishes.

Frequently asked questions

Yes, as an OpenClaw automation. The Hub has no scheduler for agent prompts, so the timer lives in OpenClaw. Use the Scan MCP for public URLs, and for your own sites prefer reading history and scanning only when the last report is old.

On xSpeed Hub, yes, because run_speed_scan is classed as a write tool. A read-only connection refuses it but still allows get_speed_scan for history. The Scan MCP needs no connection scope at all, since every one of its tools is read-only.

run_speed_scan runs the full xSpeed Scan: server probes plus Lighthouse, a 0 to 100 grade across four dimensions, the fix for every failing check and a shareable report link. run_speed_test returns a raw PageSpeed Insights score with Core Web Vitals and no graded report.

Yes, through the xSpeed Scan MCP at https://xspeedcache.com/scan/mcp. It needs no account and no sign-in, accepts any public URL and is read-only. The Hub route only scans sites you connected to your own workspace.

The Scan MCP allows 4 scans per caller per 10 minutes. Scanning the same URL again within 10 minutes returns the existing report unless the agent passes fresh: true. A Hub scan spends a shared allowance of the scan service, which is why the Hub treats it as a write tool.

Reports started from the Hub are filed as unlisted, which keeps them out of the public scan directory and search results, but the link itself still opens for anyone who has it. Reports started through the Scan MCP are public by default.

The headline grade is the desktop run, because it is the one you can reproduce in your own browser. The mobile run is graded on the same rubric and returned alongside it. Google ranks on mobile, so when the two differ the agent should tell you both.

Keep going

Scan a site's speed with other agents

More with OpenClaw

Purge the cache Find out why pages are not cached Track PageSpeed scores Raise the PageSpeed score Tune cache settings Warm the cache Set up Redis object cache Manage Cloudflare Manage every site at once

Documentation

From the blog

Scan a site's speed, from OpenClaw.

xSpeed Hub is free and has no site cap. Connect your sites once and ask from the agent you already use.

Open xSpeed Hub OpenClaw setup