Scan a website for speed problems with Muse

Scanning a site's speed with Muse means messaging Meta's personal AI agent for your site's xSpeed Scan grades, reading the history the Hub already holds, and starting a fresh scan only once you widen its access.

list_sitesget_speed_scanrun_speed_scan

Last updated: October 2026

Example session · Muse

You: Use xSpeed Hub to tell me what shop scored on its last speed scan. Short answer.

get_speed_scan(site: shop) read-only
→ Latest report 6 days old: desktop grade B, mobile grade D. Top failing check on mobile: image size. Report link included.

Muse: Desktop B, mobile D, six days ago. Mobile is held back mostly by image size. Here is the report link.

You: Can you run a new one?

Muse: Not on this connection. Your token is read-only, and the Hub refuses run_speed_scan on it because each scan spends the shared allowance. Turn Read-only everywhere off in xSpeed Hub and ask me again.

How Muse handles this

Someone tells you the shop feels slow, and you are not at your desk. You open WhatsApp and ask Muse what shop scored. With xSpeed Hub added as a custom connector, Muse calls get_speed_scan, which returns the site's scan history and a summary of the latest report without starting anything: the grade out of 100, the desktop run as the headline and the mobile run beside it, the top failing checks and the report link. That is often the whole answer, and it reads well in a chat thread.

A fresh scan is a different call. run_speed_scan runs server probes and a Lighthouse run, takes 20 to 60 seconds, and spends a shared speed-test allowance, so the Hub classes it as a write tool even though it changes nothing on your site. The setup the Muse page recommends starts the connection token on Read-only everywhere, and on that token the Hub refuses run_speed_scan. So the first weeks with Muse are history only: you can read every past report, and you cannot start a new one until you turn the switch off on the Connect AI page.

Once you do, Meta's own approval settings apply. Meta says Muse will not take many important actions without your approval by default, that you change when it asks in Settings, and that its Sentinel agent asks for permission when needed. xSpeed Hub has no confirmation step of its own, so Muse's settings are what decide whether a scan waits for you. Ask Muse for a fresh scan by name when you are re-testing after a change, because a scan of the same site within ten minutes returns the existing report.

Set up Muse once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the Muse 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.

2Copy the connection token from xSpeed Hub

Sign in at app.xspeedcache.com as the workspace owner and open Connect AI. Copy the connection token. For a first try, turn on Read-only everywhere: the Hub then refuses every write tool on that token, so Muse can read but not purge or change settings.

Text

xSpeed Hub  >  Connect AI  >  connection token (Read-only everywhere: on)

3Ask Muse to create a custom connector

Send this message to Muse in the app, on muse.ai or in WhatsApp, and follow the steps Muse gives you. When it asks for the credential, give it the token as a Bearer token. Meta does not review custom connectors, so only finish this for the request you started yourself.

Text

Create a custom connector called xSpeed Hub for the MCP server at
https://app.xspeedcache.com/xspeed/mcp
It authenticates with a Bearer token in the Authorization header. Once it is connected, use xSpeed Hub to list my sites.

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 Muse 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 Muse 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. Meta says Muse will not take many important actions without your approval by default, that many connectors can be set up to only retrieve data, and that you change when Muse asks for approval in its Settings. Muse's separate Sentinel agent also decides what leaves its secure machine and asks you for permission when needed. xSpeed Hub has no confirmation step of its own, so a write runs as soon as Muse calls it and your connection allows writes. The firm stop here is the token: with Read-only everywhere on, the Hub refuses every write tool, whatever Muse decides. Turn it off only when you want Muse to purge or change settings, and read each question Muse asks before you answer yes.

What do I ask?

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

Prompt for Muse

Use xSpeed Hub to tell me what shop scored on its last speed scan, desktop and mobile. Do not start a new one.

Prompt for Muse

With xSpeed Hub, send me the report link for blog's latest scan and its top failing check.

Prompt for Muse

Ask xSpeed Hub for a fresh speed scan of shop and tell me if mobile moved since the last report.

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 Muse

Turning Read-only everywhere off is a workspace-wide change: it lets every client that sends the token start scans and also purge, toggle and change settings on every site, so widen it for the scan you want and consider turning it back on afterwards. Meta's pages describe no scheduled tasks for Muse, so a weekly speed check happens when you message it, not on a timer. Meta's pages also do not say which protocol a custom connector uses, so this page covers the Hub route and does not walk through adding the no-account xSpeed Scan MCP for a site you do not run. A scan cannot reach private, local or password-protected sites. The report link Muse sends is unlisted for a Hub scan, which keeps it out of the public scan directory, but anyone you forward it to can open it. Muse is rolling out in the US first.

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

No. The Hub classes run_speed_scan as a write tool because it spends the shared speed-test allowance, so a token with Read-only everywhere on refuses it. get_speed_scan still works, so Muse can read every past report and its link.

Yes, if Muse is available to you there. The same custom connector serves the Muse app, muse.ai and WhatsApp. Ask for the last scan's grades and Muse reads them from the Hub without starting a new scan.

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 Muse

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 Muse.

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

Open xSpeed Hub Muse setup