Run and track PageSpeed tests with Kimi Code

Tracking PageSpeed scores with Kimi Code means asking Moonshot AI's terminal agent, in the repository where you changed the theme, for stored PageSpeed history and a fresh test of the live site through xSpeed Hub.

list_sitesget_score_historyrun_speed_testget_benchmark_historyrun_benchmark

Last updated: October 2026

Example session · Kimi Code

You: The font-loading change is live on blog. Use xSpeed Hub to tell me if mobile PageSpeed moved.

get_score_history(site: blog) read-only
→ latest mobile 60 (7 days ago), previous 59; LCP 3.6 s, FCP 2.4 s

Kimi Code: Both stored runs predate the deploy, so they cannot answer it. One fresh mobile test of the live site takes up to two minutes and spends shared allowance. Run it?

You: Approve once.

run_speed_test(site: blog, strategy: mobile) uses quota
→ mobile score 64, FCP 1.9 s, LCP 3.2 s, saved to the Hub report history

Kimi Code: Mobile is 64 against 60, and FCP dropped by half a second, which fits faster font loading. One run, so treat it as a first reading.

How Kimi Code handles this

You ran kimi in the theme repository, changed how fonts load, and deployed. The question now is whether PageSpeed noticed. Ask Kimi Code for the history of the site, and it calls mcp__xspeedhub__get_score_history and prints the stored runs: score, LCP, FCP, CLS, TBT, Speed Index and TTFB for mobile and desktop. Because it already has the diff open, it can line a metric change up with the files you touched, though that link is a guess for you to check.

For a fresh number it calls run_speed_test, a PageSpeed Insights run from the Hub, mobile or desktop, which can take up to about two minutes. It tests the live address connected to the Hub, so a change that exists only in your working copy will not show; deploy first. The result is saved in the Hub's own report history on the Reports tab, which get_score_history may not read. run_benchmark gives a quicker cached against uncached timing of the home page, with no Lighthouse score, and get_benchmark_history lines earlier runs up with your settings changes.

In the default Always Ask mode, Kimi Code asks about every MCP call that matches no permission rule, so even get_score_history prompts until a rule allows it. Add allow rules in [[permission.rules]] in config.toml for mcp__xspeedhub__get_* and mcp__xspeedhub__list_*, and leave run_speed_test unmatched so each test still asks. A server added mid-session joins only the next one, so restart kimi after you edit mcp.json.

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

1 / 3

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

Using xSpeed Hub, what are the stored mobile and desktop scores for shop, and how old is the newest run?

Prompt for Kimi Code

I deployed the font change to blog. Use xSpeed Hub to run one mobile test and compare it with the last stored run.

Prompt for Kimi Code

With xSpeed Hub, show the benchmark history for shop next to the settings changes from this week.

What happens, step by step

PageSpeed Insights is Google's Lighthouse audit, and its score and Core Web Vitals are the numbers most people mean by "my speed". Through xSpeed Hub an agent can read the scores a site has already stored, run a new PageSpeed test on mobile or desktop, and read or run a separate benchmark of cached against uncached response time. The three answer different questions, and the Hub tells the agent which to use for each.

Read before you test

get_score_history returns the stored PageSpeed Insights and GTmetrix runs for a site: the score per run, with LCP, FCP, CLS, TBT, Speed Index and TTFB, mobile and desktop. It starts nothing. The Hub tells the agent to use it whenever you ask what your score is, or whether it improved, because a new test spends a shared allowance.

Run a new test when you need one

run_speed_test runs a real PageSpeed Insights audit on the site from the Hub and returns the score, the Core Web Vitals and the top opportunities. strategy is mobile (the default) or desktop, and one call tests one of them. It can take up to about 2 minutes, so the agent should say it is running before it calls.

Test the other device

Mobile and desktop scores differ, often by a lot. For both, the agent makes two calls, one per strategy. A failure is reported with its reason: PageSpeed not configured, quota reached, a timeout, or a site the audit cannot reach.

Measure the cache on its own

run_benchmark times the home page with the cache bypassed and again served from cache, and returns the response times. It is a read tool, and it accepts site: "all" for every site. It does not return a Lighthouse score, so the agent must not use it to answer a PageSpeed question.

Compare over time

get_benchmark_history returns past benchmark runs, uncached against cached, together with the settings changes on the same timeline, which is how you answer "did that change help?". For PageSpeed scores over time, use get_score_history.

Reference

Read stored scores	get_score_history (read): PageSpeed Insights and GTmetrix runs, starts nothing
Metrics per run	Score, LCP, FCP, CLS, TBT, Speed Index, TTFB, for mobile and desktop
Run a new test	run_speed_test (write, uses the shared allowance): one PageSpeed Insights run per call
strategy	mobile (default) or desktop
Duration	Up to about 2 minutes per run
Why a test is a write	It spends a shared PageSpeed allowance and stores a report; it changes nothing on the site
Read-only access	A connection token with Read-only everywhere on, or a Viewer member's sign-in: run_speed_test is refused; get_score_history, run_benchmark and get_benchmark_history still work. An OAuth sign-in gets the scopes the client asks for
Benchmark	run_benchmark (read): cached against uncached response time for the home page, no Lighthouse score
Benchmark history	get_benchmark_history (read): past runs plus settings changes on the same timeline
Scheduling	The Hub does not schedule PageSpeed tests itself; its daily pass only reads reports the plugin already stored
Where a new test is stored	In the Hub's own report history, the one the Hub dashboard shows

Rules worth keeping

Check the history first. Ask for stored scores before starting a test, and run a new one only when you want a fresh measurement or something changed.
Never answer a PageSpeed or Lighthouse question with run_benchmark. It times your own cache and carries no score.
run_speed_test changes nothing on your site, but the Hub classes it a write because it spends a shared allowance. A connection token with Read-only everywhere on, or a Viewer sign-in, refuses it. An OAuth sign-in gets the scopes the client asks for, so there your client's approval prompt is the gate.
Lab scores move a few points between runs of the same page. The agent should compare like with like, same site, same strategy, and not report one run's difference as a trend.
A new test does not run on a timer. If you want a regular test, the agent has to be started by something else, such as a scheduled job in your client, and a scheduled run that spends the allowance should be one you are comfortable leaving unattended.

Good to know with Kimi Code

Approve for this session is convenient and easy to over-use: approve run_speed_test that way and every later test in the session runs without asking, each spending the shared allowance. Ask When Needed mode, from /yolo, approves MCP calls automatically, and Never Ask, from /auto, approves everything, so a request like "retest after each change" would loop with no prompt, because the Hub has no confirmation step of its own. Avoid one wildcard rule for the whole server, which would allow the test too. If a session should only read, list the read tools in the entry's enabledTools, or send a connection token with Read-only everywhere on through bearerTokenEnvVar; the Hub then refuses run_speed_test. Say how many tests you want in the request as well.

More prompts for this job

They work in any client connected to xSpeed Hub.

Prompt

Using xSpeed Hub, what is the mobile PageSpeed score for shop? Check the stored history before you run anything.

Prompt

Use xSpeed Hub to run a new mobile PageSpeed test on blog and tell me the score, LCP and the top opportunities.

Prompt

With xSpeed Hub, test shop on desktop and mobile and tell me which one is worse.

Prompt

Using xSpeed Hub, has the PageSpeed score on docs improved over the last few runs?

Prompt

Use xSpeed Hub to benchmark the cache on every site and tell me which one saves the least time.

Prompt

Did turning on minification on shop help? Use xSpeed Hub to compare the benchmark history around that change.

Prompt

My PageSpeed test failed on staging. Use xSpeed Hub to tell me why.

Frequently asked questions

In Always Ask mode it prompts for any MCP call that no permission rule allows, reads included. Add an allow rule in config.toml whose pattern matches the Hub's get_ tools, which Kimi Code names mcp__xspeedhub__ followed by the tool name, so get_score_history runs quietly, and leave run_speed_test without a rule so each test still asks.

No. run_speed_test measures the live address connected to xSpeed Hub, through PageSpeed Insights on Google's side. A change only in your working copy cannot be reached, so deploy before you ask for the test.

run_speed_test runs a real PageSpeed Insights audit and returns a Lighthouse score with Core Web Vitals. run_benchmark measures how fast your own cache answers compared with an uncached request for the home page, and returns no Lighthouse score. Use the first for "what is my PageSpeed score" and the second for "is my caching working".

A single run can take up to about 2 minutes, so the agent should tell you it has started before it calls. One call tests one device, mobile or desktop, so checking both takes two calls.

Yes. get_score_history reads the stored PageSpeed Insights and GTmetrix runs for the site and starts nothing. The Hub tells the agent to read it first whenever you ask what your score is, because a new test spends a shared allowance.

No. The Hub does not schedule PageSpeed tests itself. Its daily pass re-verifies sites, snapshots cache status and pulls the PageSpeed and GTmetrix reports the plugin has already stored, and it can alert on a score regression. If you want regular new tests, they have to be started by a client that can run scheduled jobs.

It does not change your site. The Hub classes run_speed_test as a write because it spends a shared PageSpeed allowance and stores a report, and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) should not be able to cost the owner anything. Such a connection can still read stored scores with get_score_history.

Track PageSpeed scores, 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

Run and track PageSpeed tests with Kimi Code

How Kimi Code handles this

Set up Kimi Code once

What do I ask?

What happens, step by step

Reference

Rules worth keeping

More prompts for this job

Frequently asked questions

Keep going

Track PageSpeed scores, from Kimi Code.