Scan a website for speed problems with Kimi Code

Scanning a site's speed with Kimi Code means asking Moonshot AI's terminal agent to read a site's xSpeed Scan history, run a fresh graded scan after your change, and tell you which grade moved.

list_sitesget_speed_scanrun_speed_scan

Last updated: October 2026

Example session · Kimi Code

You: I deployed the header change to shop. Use xSpeed Hub to compare it with the last scan.

get_speed_scan(site: shop) read-only
→ Previous report: desktop grade B, mobile grade D. Top failing check: render-blocking stylesheet

run_speed_scan(site: shop, fresh: true, strategy: both) uses quota
→ Desktop grade B, mobile grade C. Render-blocking stylesheet passes; top failing check: image size. Report link included.

Kimi Code: Mobile moved from D to C and desktop held at B. The stylesheet check passes now, so the header change worked. The next item is image size on the homepage, and I can find the hero image in the theme.

You: Do it, then stop. No more scans today.

Kimi Code: Understood. I will resize and preload the hero image in the template and leave the next scan to you.

How Kimi Code handles this

The moment comes at the end of a change. Kimi Code has edited the theme, you deployed it, and you want a number before you call it done. You ask the agent to compare the site before and after. It calls mcp__xspeedhub__get_speed_scan first, which returns the scan history and the latest report and spends nothing, then mcp__xspeedhub__run_speed_scan with fresh set to true, so the scan service measures again instead of reusing a report from the last ten minutes.

The result is a grade out of 100 from server probes and a Lighthouse run, with the desktop run as the headline and the mobile run beside it, the failing checks ranked by points recoverable and a report link. Because Kimi Code has your repository open, it can map a failing check to a file: a render-blocking stylesheet in the theme's header template, a hero image served at full size. For a site you do not run, add the no-account xSpeed Scan MCP as a second entry in mcp.json with just its url; it is read-only and allows four scans per caller per ten minutes.

In Kimi Code's default Always Ask mode, an MCP call that matches no permission rule asks for approval. That suits scans: add an allow rule for mcp__xspeedhub__get_* in [[permission.rules]] so history reads run quietly, and leave run_speed_scan on the prompt, because the Hub classes it as a write tool that spends the shared speed-test allowance. Every tool on the Scan MCP is a read, so allowing that server's tools costs nothing but its scan limit.

Set up Kimi Code once

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

2Add xSpeed Hub to mcp.json

Put this in ~/.kimi-code/mcp.json to use the Hub in every project, or in .kimi-code/mcp.json inside one repository, where it overrides a user entry of the same name. You can also run /mcp-config and let Kimi Code add it. A server added while a session is open joins only the next session.

~/.kimi-code/mcp.json

{
  "mcpServers": {
    "xspeedhub": {
      "url": "https://app.xspeedcache.com/xspeed/mcp"
    }
  }
}

3Sign in with /mcp-config login

Start a new session with kimi, run this and approve access on the xSpeed Hub page that opens in your browser. There is no token to paste. Then run /mcp to check that xspeedhub is connected.

Text

/mcp-config login xspeedhub
/mcp

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 Kimi Code 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 Kimi Code 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. In Kimi Code's default Always Ask mode, an MCP call that matches no permission rule asks for approval, and Approve for this session allows the same kind of call until the session ends. Permanent rules go in [[permission.rules]] in config.toml: allow mcp__xspeedhub__get_* and mcp__xspeedhub__list_* to let the reads run, and leave the write tools on the prompt. Ask When Needed mode, from /yolo, approves MCP calls automatically, and Never Ask, from /auto, approves everything. xSpeed Hub has no confirmation step of its own, so in either of those modes a purge or a settings change runs as soon as your connection allows writes. To remove writes altogether, list the read tools in the entry's enabledTools, or use a connection token with Read-only everywhere on.

What do I ask?

Three prompts written for Kimi Code. More for this job are below.

Prompt for Kimi Code

Use xSpeed Hub to read shop's last scan, then run one fresh scan after my deploy and tell me which grade moved.

Prompt for Kimi Code

With the xSpeed Scan MCP, grade the public staging URL and map the failing checks to files in this repo.

Prompt for Kimi Code

Using xSpeed Hub, what did blog score on its last three scans? Read the history only.

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 Kimi Code

Ask When Needed mode, from /yolo, approves MCP calls automatically, and Never Ask, from /auto, approves everything, so in either mode an agent told to keep trying until the grade improves can start scan after scan, each spending the allowance. Approve for this session on run_speed_scan has the same effect until the session ends. xSpeed Hub has no confirmation step of its own, so give the agent a stopping rule, such as one scan before the change and one after. A connection token with Read-only everywhere on, sent through bearerTokenEnvVar, makes the Hub refuse run_speed_scan whatever the mode, and a Viewer sign-in does the same for an OAuth login. The scan runs from the xSpeed servers, so it measures the deployed site: edits that are only on your machine do not change the grade, and a local or password-protected preview cannot be scanned at all. A server added mid-session joins only the next session.

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

Stay in Always Ask mode and allow only the Hub's read tools, such as mcp__xspeedhub__get_speed_scan, in your permission rules, so run_speed_scan still prompts. Avoid /yolo and /auto for scan work, and for a hard stop use a token with Read-only everywhere on.

No. A scan runs from the xSpeed servers, so the URL has to be public. Deploy the change, then ask for a fresh scan of the live site.

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 Kimi Code

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 Kimi Code.

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

Open xSpeed Hub Kimi Code setup