xSpeed Cache is officially live! Get 50% OFF during Launch Week — Lifetime starts at just $79Lifetime from $79 — 50% OFF, Launch Week! See Plans →

See Plans →
Features
xSpeed Hub Pricing Docs Blog Scan
Appearance
Get Plugin

Scan a website for speed problems with Grok Bot

Scanning site speed with Grok Bot means giving a named xAI Bot a routine that reads xSpeed Scan history for your sites, scans when a report is stale and posts the grades with their links.

list_sitesget_speed_scanrun_speed_scan

Last updated: October 2026

Example session · Grok Bot

You: Use @xspeedhub (xSpeed Hub) to check shop's speed, and scan it only if the last report is over a week old.

get_speed_scan(site: shop) read-only
→ Latest report 3 days old: desktop grade B, mobile grade C. 8 scans in history.

Grok Bot: The latest report is three days old, so I did not start a scan. Desktop B and mobile C, the same as the week before. The top failing check on mobile is image size.

You: Make that a routine for every Monday.

Grok Bot: Routine saved for Mondays at 9:00. It reads the history first and scans only when the latest report is over a week old. The next run is on Monday.

01

How Grok Bot handles this

A Grok Bot keeps its context and runs on a persistent cloud computer, so it can own the slow, repetitive part of speed work: noticing when a grade moves. You attach the xspeedhub plugin and ask the Bot to watch shop. It starts with get_speed_scan, which returns the scan history and the latest report summary and spends nothing. If the latest report is older than you allow, it calls run_speed_scan for a fresh graded scan, and because it keeps context it can tell you next time what moved since the last grade.

The routine is where this pays off. You tell the Bot when to run and what to report, it creates the routine and shows its next run, and background routines run while your laptop is closed. The Hub has no scheduler for agent prompts, so the timer is the Bot's. For competitors, add the no-account xSpeed Scan MCP as a second remote HTTPS MCP server; it grades any public URL, is read-only, and allows four scans per caller per ten minutes, so a routine covering several competitors should space its scans out.

Each scan returns a grade out of 100 with the desktop run as the headline and the mobile run beside it, the failing checks ranked by points recoverable, and a report link. On the Hub, run_speed_scan is classed as a write tool because it spends the shared speed-test allowance, even though it changes nothing on your site. Grok Bot offers Allow once, Always allow or Deny when an action needs approval, and Auto-review rules can force Ask first on the calls you name.

02

Set up Grok Bot once

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

2Ask your Bot to add xSpeed Hub

In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI says a plugin you add from your own chat is personal and account-wide, so every Bot on your account can use it. When the browser opens, approve access on the xSpeed Hub page.

Text
Add a custom remote HTTPS MCP server called xspeedhub with the URL https://app.xspeedcache.com/xspeed/mcp and sign me in.

3Attach it and ask a first question

Type @ in a chat to attach the xspeedhub plugin to the task, then ask something that names xSpeed Hub. A list of your sites means the connection works.

Text
Use @xspeedhub (xSpeed Hub) to list my sites and tell me which ones have page caching turned off.

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 Grok Bot 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 Grok Bot 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. When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, so the same kind of call no longer stops for you. Auto-review rules under Settings, General, Auto-review can force Ask first or allow matching actions automatically, and Ask first wins when both match. xSpeed Hub has no confirmation step of its own, so a Hub write tool you always allow runs as soon as your connection allows writes. Add Ask first rules for purge_cache, update_settings, toggle_cache, optimize_site and the other write tools. For read-only access, sign in as a Viewer member of the workspace.

03

What do I ask?

Three prompts written for Grok Bot. More for this job are below.

Prompt for Grok Bot
Every Monday, use @xspeedhub (xSpeed Hub) to read shop's scan history and scan only when the latest report is over a week old.
Prompt for Grok Bot
Use the xSpeed Scan MCP to grade [competitor URL] once a week and post the desktop and mobile grades with the report link.
Prompt for Grok Bot
With xSpeed Hub, compare blog's last two scans and tell me if they graded the same device before you tell me what changed.
04

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.

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

05

Reference

Hub routerun_speed_scan, then get_speed_scan with scan_id; only for sites connected to your Hub
Scan MCP routehttps://xspeedcache.com/scan/mcp, no account, 5 tools, read-only, any public URL
Scan MCP limit4 scans per caller per 10 minutes
Why run_speed_scan is a writeIt spends a shared scan allowance and stores a report; it changes nothing on the site
Read-only Hub connectionrun_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
Duration20 to 60 seconds; the Hub waits about 50 seconds, then returns a scan id
Poll argumentscan_id on the Hub tool, scanId on the Scan MCP tool
strategyboth (default), desktop or mobile; one device costs half the quota and becomes the headline
freshtrue forces a new measurement; otherwise a report from the last 10 minutes is reused
Report linkxspeedcache.com/scan/r/<id>; add .md for a Markdown twin an agent can read
Report visibilityHub scans are filed unlisted; Scan MCP scans are public in the scan directory by default
06

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 Grok Bot

Decide before the first routine how often it may spend a scan. Always allow on run_speed_scan saves a rule, so every later routine run scans without stopping, and xAI notes that a routine's Test run performs real work too, including calls to connected tools. xSpeed Hub has no confirmation step of its own, so the rule in the routine's wording (scan only if the latest report is older than seven days) and an Ask first rule are what keep the allowance in check. A Viewer member's sign-in refuses run_speed_scan, which suits a Bot that should only report; the plugin signs in with OAuth, so the Read-only everywhere switch on the connection token does not apply. A plugin added from your own chat is account-wide, so every Bot on your account can start Hub scans through it. Scans through the Scan MCP are public in the scan directory by default, so a routine that tracks competitors leaves reports anyone with the link can open.

07

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

Frequently asked questions

Yes. Background routines run on the Bot's cloud computer. Have the routine read the scan history first and start a scan only when the latest report is old, because each Hub scan spends the shared allowance.

Only if you accept that every later call scans without stopping, routines included. An Ask first rule keeps the prompt. get_speed_scan, which reads history and spends nothing, is the one to always allow.

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.

09

Keep going

Scan a site's speed with other agents

More with Grok Bot

Documentation

From the blog

Scan a site's speed, from Grok Bot.

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