# Raise a WordPress site's PageSpeed score with Grok Bot

> Raising a WordPress PageSpeed score with Grok Bot means attaching xSpeed Hub to a Bot, approving the optimization pass it previews, and letting it open the pages to check in the browser on its own cloud computer.

Page: https://xspeedcache.com/agent/grok-bot/optimize-site/
Last updated: October 2026

The verify step is where a Bot earns its place in this job. You attach the xspeedhub plugin with @ and ask the Bot to raise the score on the portfolio site, preview first. It calls optimize_site with dry_run on and posts the plan in the chat: the settings xSpeed would turn on at the standard level, with nothing changed. Grok Bot offers Allow once, Always allow or Deny when an action needs approval, so the preview is also the first approval card you see.

You approve the real pass. It measures the site, applies each setting one at a time, checks the page after each, and undoes anything that breaks it, for up to about two minutes. The result names the verify_urls, and the Hub tells the agent to open them and check that each page renders and the console is clean. Grok Bot's cloud computer has a browser, so the Bot can load those pages itself and tell you what it saw: which pages render cleanly, and which one logs an error after script deferral. That turns a list of URLs into a first-pass check you can act on.

Treat the Bot's look as a first pass, not the last word. Its browser is one machine in a cloud, not your visitors' phones, so open one or two of the pages yourself before you call the run done. If the site has the Pro Critical CSS module, the Bot can generate critical CSS next and purge the cache so pages rebuild with it, each as its own approved step.

## Set up Grok Bot once

### 1. Put 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.

### 2. Ask 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.

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

### 3. Attach 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.

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

Full setup: https://xspeedcache.com/agent/grok-bot/

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

## Prompts

- Use @xspeedhub (xSpeed Hub) to preview an optimization for portfolio at the standard level. Stop after the plan.
- With xSpeed Hub, apply the plan to portfolio, then open each verify URL in your browser and tell me what the console shows.
- Every Friday, use xSpeed Hub to read the stored PageSpeed history for each site and report any drop. Report only.

## Example session

```
You: Use @xspeedhub (xSpeed Hub) to raise the PageSpeed score on portfolio. Preview first, then check the pages yourself.
  → optimize_site(site: portfolio, aggressiveness: standard, dry_run: true) [dry run]: plan: 4 settings to apply (CSS minify, defer JS, lazy-load images, compression), nothing changed
Agent: The plan is CSS minify, script deferral, lazy-loading and compression. Nothing has changed. Apply it to portfolio?
You: Yes, apply it.
  → optimize_site(site: portfolio, aggressiveness: standard) [changes site]: applied 4, undone 0, unfixable: autoplay gallery video; verify_urls: home, gallery, contact
Agent: All four settings are on. I opened the three verify URLs in the browser on my computer: home and gallery render with a clean console, and the contact page logs one error from the form script. Try the contact form yourself before we keep script deferral.
```

## How it works

1. **See where the site stands**: The agent reads get_score_history for the last stored scores and list_modules for which modules exist on that site and what state they are in. Neither changes anything.
2. **Preview with dry_run**: optimize_site with dry_run: true returns the plan: each change and its tier, what would be skipped (already on, or needing a higher aggressiveness) and what it cannot fix. Nothing is applied. The tool description tells the agent to prefer this before the first real run on a site you have not optimized before.
3. **Apply it**: optimize_site without dry_run applies the plan. aggressiveness is safe (removals and server-side changes only), standard (the default) or aggressive, which includes settings known to break some themes and should be opted into deliberately. A run can take up to about 2 minutes per site.
4. **Look at the site afterwards**: When changes were applied, the result carries verify_urls and a note. The site checks its own HTML and reverts anything that breaks it, but it cannot run JavaScript, so verified: true does not prove the page works in a browser. The Hub tells the agent to open those URLs and check the page renders and the console is clean, or to tell you which URLs to check.
5. **Reach for a number only if you named one**: target_score (1 to 100, Pro sites only) turns one pass into repeated rounds toward that score, up to max_rounds, with 3 as the most per site. Each round is a real PageSpeed measurement and up to about 2 minutes. The result says why it stopped, and diminishing returns means what is left is outside what caching can reach.
6. **Critical CSS on Pro sites**: generate_critical_css generates above-the-fold CSS so the first screen can paint without waiting for the full stylesheets. It needs the Pro Critical CSS module on that site, and the site answers with an unknown-tool error without it. Pages are rebuilt with it on their next build, so the agent purges the cache afterwards.

## Reference

| | |
| --- | --- |
| Main tool | optimize_site (write): measure, apply one setting at a time, verify, undo what breaks, re-measure |
| Preview | dry_run: true returns the plan and changes nothing |
| aggressiveness | safe, standard (default) or aggressive |
| Every site at once | site: "all" or a list of handles, one result per site, sites run one after another; the Hub's confirm-once instruction does not name optimize_site, so your client's prompt is the gate |
| Time | Up to about 2 minutes per site |
| target_score | 1 to 100; needs Pro on the site; without it the site runs one pass and says so |
| max_rounds | Up to 3 per site; only sent along with target_score; 12 rounds in total per call |
| Wide fan-out with a target | Each site gets fewer rounds, and the result carries a note saying so |
| Result fields | applied, skipped, reverted, unfixable, score, verified, rounds; verify_urls after a run that changed something |
| Already tuned site | Returns "everything is already on" plus what it cannot fix; that is an answer, not a failure |
| Critical CSS | generate_critical_css (write), Pro Critical CSS module required; purge_cache afterwards |
| Read-only connection | optimize_site and generate_critical_css are refused; dry_run is still a write call, so it is refused too. Applies to the connection token with Read-only everywhere on and to a Viewer sign-in, not to other OAuth sign-ins |

## Rules

- Run dry_run first. optimize_site changes live site settings as soon as your connection allows writes. The tool description tells the agent to preview first on a site that has not been optimized, but that is guidance, so your client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the real gates.
- Keep aggressive for a deliberate choice. It includes settings known to break some themes, and the agent should say so before using it.
- After a run that changed something, open the pages in verify_urls. The HTML checks cannot run JavaScript, so a page can pass them and still be broken in a browser. Do not call a run safe because verified is true.
- Relay the unfixable list. When a site is already tuned, the honest answer is that caching is done and the rest is page weight, hotlinked images or DOM size. The agent should not retry the tool or claim a gain it did not make.
- Only ask for target_score when you want the site driven to a number. Each round costs a real PageSpeed measurement, and a plain "make it faster" is one pass.

## Good to know with Grok Bot

Choose Allow once on optimize_site, not Always allow. The dry run and the real pass are the same tool, so an Always allow saved while you approve the preview lets the real pass through with no card, and xSpeed Hub has no confirmation step of its own to catch it. Add an Ask first rule under Settings, General, Auto-review for optimize_site, generate_critical_css and purge_cache; Ask first wins when an automatic allow also matches. Keep routines to reads: a routine can watch get_score_history and report a drop, but a scheduled optimize_site runs with nobody to read the plan, and a routine's Test run does real work, calling connected tools for real. A Viewer sign-in refuses optimize_site entirely, dry run included.

## More prompts for this job

They work in any client connected to xSpeed Hub.

- Ask xSpeed Hub to preview what optimize_site would change on shop with a safe pass. Do not apply anything.
- Use xSpeed Hub to optimize the blog site with the standard pass, then give me the pages to check by hand.
- With xSpeed Hub, get docs to a mobile PageSpeed score of 90 if you can, and tell me why it stopped if it does not get there.
- Use xSpeed Hub to show me what optimize_site would do on every site, as a dry run, and list which sites have the most left to change.
- Use xSpeed Hub to generate critical CSS for shop, then purge the cache so the pages are rebuilt with it.
- With xSpeed Hub, optimize shop, then compare the new PageSpeed score with the last stored one.
- Using xSpeed Hub, what could optimize_site not fix on the shop site?

## Frequently asked questions

### Can Grok Bot check the pages after an xSpeed optimization?

It can make a first pass. Its cloud computer has a browser, so it can open the verify URLs the run returns and report what renders and what the console shows. Open one or two pages yourself as well, because its browser is not your visitors' devices.

### Should I always allow optimize_site in Grok Bot?

No. The preview and the real pass are the same tool, so Always allow on the preview also lets the real pass run without a card. Choose Allow once, and add an Ask first rule for optimize_site in Auto-review.

### What does optimize_site actually do?

It measures the site, applies the recommended xSpeed settings one at a time, checks that the page still renders after each change, and undoes any change that breaks it. It then reports what was applied, skipped and reverted, and what it could not fix. It reaches caching and asset delivery only.

### Should I run a dry run first?

Yes, especially on a site you have not optimized before. dry_run: true returns the plan, what would be skipped and what cannot be fixed, and changes nothing. The tool description tells the agent to prefer it, but nothing forces it, so say so in your prompt if you want a preview.

### Can I tell it to get my site to a score of 90?

Yes, with target_score, on a site that has xSpeed Pro. It repeats measure, apply and re-measure for up to 3 rounds per site and stops early when rounds stop helping, saying why. On a Free site the score target is ignored and you get a single pass with a note that no iterative tuner is installed.

### Why did it say everything is already on?

That is a real answer. The settings it can apply were already enabled, so there was nothing to change. The result also lists what it could not fix, such as page weight, images hosted on another domain or DOM size, and those need changes outside a caching plugin.

### Does the agent check that my pages still work?

The site checks its own HTML after each change and reverts anything that breaks it, but it cannot run JavaScript. After a run that changed something, the Hub tells the agent to open the returned verify_urls and check the page renders and the console is clean, or to give you the URLs to check yourself.

### Does generate_critical_css work on a Free site?

No. It needs the Pro Critical CSS module on that site, and without it the site answers with an unknown-tool error. On a Pro site, purge the cache afterwards, because pages already cached were built without the critical CSS.

## Raise the PageSpeed score with other agents

[Claude Code](https://xspeedcache.com/agent/claude-code/optimize-site/) · [Claude](https://xspeedcache.com/agent/claude/optimize-site/) · [Claude Cowork](https://xspeedcache.com/agent/claude-cowork/optimize-site/) · [ChatGPT](https://xspeedcache.com/agent/chatgpt/optimize-site/) · [Codex](https://xspeedcache.com/agent/codex/optimize-site/) · [Cursor](https://xspeedcache.com/agent/cursor/optimize-site/) · [GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/optimize-site/) · [Windsurf](https://xspeedcache.com/agent/windsurf/optimize-site/) · [Gemini CLI](https://xspeedcache.com/agent/gemini-cli/optimize-site/) · [Antigravity](https://xspeedcache.com/agent/antigravity/optimize-site/) · [Zed](https://xspeedcache.com/agent/zed/optimize-site/) · [Kiro](https://xspeedcache.com/agent/kiro/optimize-site/) · [OpenCode](https://xspeedcache.com/agent/opencode/optimize-site/) · [OpenClaw](https://xspeedcache.com/agent/openclaw/optimize-site/) · [Hermes Agent](https://xspeedcache.com/agent/hermes-agent/optimize-site/) · [Grok Build](https://xspeedcache.com/agent/grok-build/optimize-site/) · [ChatGPT dots](https://xspeedcache.com/agent/chatgpt-dots/optimize-site/) · [Grok](https://xspeedcache.com/agent/grok/optimize-site/) · [Muse](https://xspeedcache.com/agent/muse/optimize-site/) · [Manus](https://xspeedcache.com/agent/manus/optimize-site/) · [Kimi Code](https://xspeedcache.com/agent/kimi/optimize-site/) · [Paperclip](https://xspeedcache.com/agent/paperclip/optimize-site/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/optimize-site/)

## More with Grok Bot

- [Purge the WordPress cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/purge-cache/)
- [Find out why WordPress pages are not cached with Grok Bot](https://xspeedcache.com/agent/grok-bot/troubleshoot-cache/)
- [Scan a website for speed problems with Grok Bot](https://xspeedcache.com/agent/grok-bot/speed-scan/)
- [Run and track PageSpeed tests with Grok Bot](https://xspeedcache.com/agent/grok-bot/pagespeed-tests/)
- [Tune WordPress cache settings with Grok Bot](https://xspeedcache.com/agent/grok-bot/cache-settings/)
- [Warm the WordPress cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/preload-cache/)
- [Set up the Redis object cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/object-cache/)
- [Manage Cloudflare caching with Grok Bot](https://xspeedcache.com/agent/grok-bot/cloudflare/)
- [Manage every WordPress site at once with Grok Bot](https://xspeedcache.com/agent/grok-bot/fleet/)

## Documentation

- How to generate Critical CSS: https://xspeedcache.com/docs/critical-css/
- Performance recommendations: https://xspeedcache.com/docs/performance-recommendations/
- How to run a speed test: https://xspeedcache.com/docs/external-score/
- Free vs Pro: what is included: https://xspeedcache.com/docs/free-vs-pro/