# Find out why WordPress pages are not cached with Antigravity

> Finding out why pages are not cached with Antigravity means asking its agent to read xSpeed cache status, health checks and a benchmark through xSpeed Hub, and to tell a real fault from pages that are meant to skip the cache.

Page: https://xspeedcache.com/agent/antigravity/troubleshoot-cache/
Last updated: October 2026

You have the shop's theme open in Antigravity, and you tested the cart and checkout pages: BYPASS, every time. It looks like caching is off. You ask the agent: cart and checkout never hit the cache on shop, is something wrong?

It reads get_cache_status, get_health and run_benchmark. Caching is on, the hit ratio is healthy and the home page hit the cache. The checks pass. The agent then explains the part the tools cannot show: xSpeed excludes /cart, /checkout and /my-account by default, because a cached copy of a basket would be wrong for the next shopper. A bypass there is a pass. If a product page bypasses instead, that one is worth chasing, and it needs the response headers for that URL.

The Hub reports on the live site connected to it, not on the copy running in your local preview, so a local dev server can behave differently. Antigravity runs unconfigured MCP tools in Ask mode, so each call waits for your approval in a card. The Turbo permission preset allows MCP actions without asking, and so does an allow rule such as mcp(xspeedhub/get_health) for that one tool, so a diagnosis you leave unattended needs one of those. If you want more than a verdict, ask the agent to list which pages it expects to bypass and which it expects to cache, and to say how it knows. It can reason from the defaults, but only a request to the real URL proves the point, so treat its list as a hypothesis to test.

## Set up Antigravity 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. Add xSpeed Hub to mcp_config.json

Antigravity reads ~/.gemini/config/mcp_config.json for every project, or .agents/mcp_config.json inside one workspace. In the IDE, open the ... menu at the top of the agent side panel, choose MCP Servers, then Manage MCP Servers and View raw config. Remote servers must use the serverUrl field; the older url and httpUrl fields are not supported.

File: `~/.gemini/config/mcp_config.json`

```json
{
  "mcpServers": {
    "xspeedhub": {
      "serverUrl": "https://app.xspeedcache.com/xspeed/mcp"
    }
  }
}
```

### 3. Authenticate

Open Agent settings with Cmd+, on macOS or Ctrl+, on Windows and Linux, go to the Customizations tab and click Authenticate next to xspeedhub. Sign in to xSpeed Hub in the browser and approve access, copy the authorization code the page shows, paste it into the settings panel and click Submit. Antigravity keeps the credentials it receives and refreshes them. In the CLI, type /mcp to open the MCP manager and check the server status.

```
Settings → Customizations → Authenticate
```

Full setup: https://xspeedcache.com/agent/antigravity/

### 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. Antigravity runs unconfigured MCP tools in Ask mode, so each call waits for your approval in a card before it executes. Allow rules such as mcp(xspeedhub/get_cache_status) or mcp(xspeedhub/*) let calls through without a prompt, Ask and Deny rules take precedence over Allow, and the Turbo permission preset allows MCP and web actions without asking. When you approve a card you can also edit its target to widen the grant. With Turbo or a broad allow rule, a write reaches the Hub as soon as your connection allows writes. xSpeed Hub has no confirmation step of its own.

## Prompts

- Cart and checkout show BYPASS on shop. Using xSpeed Hub, is caching broken, or is that expected?
- Use xSpeed Hub to run the benchmark and the health report on shop and tell me whether the home page is cached.
- A product page on shop bypasses the cache. What should I check, and what can you read from xSpeed Hub?

## Example session

```
You: Cart and checkout always say BYPASS on shop. Ask xSpeed Hub whether caching is off.
  → get_cache_status(site: shop) [read-only]: page cache on, 164 cached pages, hit ratio 68% in the last 24h
  → get_health(site: shop) [read-only]: all environment checks pass
  → run_benchmark(site: shop) [read-only]: home page: 505 ms uncached, 63 ms cached, cached request was a hit
Agent: Caching is on and healthy. Cart and checkout are excluded by default, because a cached copy of a basket would be wrong for the next shopper, so BYPASS there is the expected result. If a product page bypasses, send me that URL and what its response headers say.
```

## How it works

1. **Start with the quick summary**: get_cache_status returns whether page caching is on, the stats (cached pages, size, hit ratio, last purge) and the web server xSpeed detected. It is a glance. If caching is off, or the hit ratio is far below what you expect, the agent moves on to the diagnostic.
2. **Run the diagnostic**: get_health is the tool for troubleshooting. It returns the environment checks with pass or warn tones (the advanced-cache.php drop-in, the WP_CACHE constant, rewrite rules, PHP and WordPress versions, caching plugin conflicts), the cache stats, 24 hourly hit and miss buckets and a 30-day hit-ratio series. The Hub tells the agent to use it, not get_cache_status, when you are troubleshooting rather than glancing.
3. **Time cached against uncached**: run_benchmark requests the home page once with the cache bypassed and once normally, after a warm-up request, and returns the timings. If the second request still is not a cache hit, the page cache is not serving the home page, and the result says so. It measures xSpeed's own response time. It does not return a Lighthouse score.
4. **Read what the checks mean**: A warn is a lead, not always a fault. A static-file rewrite warning, for example, can mean the nginx snippet is not in your server config yet, or that xSpeed could not verify it, which is not evidence the config is wrong. The agent reads the detail line and tells you which one it is.
5. **Fix it or hand it over**: If caching is simply off, toggle_cache turns it on. If another caching plugin owns the drop-in, the site refuses to enable xSpeed and says why; removing the other plugin is yours to do. If nothing explains it, contact_support emails xSpeed support with the agent's summary, after the agent has confirmed the message with you.

## Reference

| | |
| --- | --- |
| Quick check | get_cache_status (read): cache on or off, stats, detected web server |
| Diagnostic | get_health (read): environment checks, 24 hourly buckets, 30-day hit-ratio series, recent activity |
| One site per call | get_health does not accept site: "all"; call it for each site you care about |
| Benchmark | run_benchmark (read): home page only, cache bypassed against cache served, timings in milliseconds |
| Benchmark on every site | run_benchmark accepts site: "all" or a list of handles, one result per site |
| Benchmark history | get_benchmark_history reads past runs and the settings changes on the same timeline |
| Pro suggestions | get_pro_audit (read): which Pro features would help this site, from its settings and stats |
| Hit ratio scope | Counts requests that reach your server; pages answered by a CDN or Cloudflare edge are not counted |
| Support | contact_support emails xSpeed support with your account email and site list attached; classed read |
| Turning caching on | toggle_cache (write); refused by the site when another plugin owns the cache drop-in |

## Rules

- Diagnose with the read tools first. get_cache_status, get_health, run_benchmark and get_pro_audit change nothing on the site, so a read-only connection can run all of them. For clients that send the connection token, that means Read-only everywhere on; an OAuth sign-in gets the scopes the client asks for, unless the member is a Viewer.
- Do not answer a PageSpeed question with run_benchmark. It measures cached against uncached response time and returns no Lighthouse score; for a score, use the speed test or scan jobs.
- toggle_cache is a write. It runs as soon as your connection allows writes, and the Hub tells the agent to confirm the target site first. That is guidance to the agent, so your client's approval prompt is the gate that matters.
- contact_support sends a real email. The Hub tells the agent to confirm the message with you before sending, but the tool is classed read, so even a read-only connection can send one.
- The agent cannot edit your server configuration or another plugin's settings. When a check needs an nginx snippet or a conflicting plugin removed, it tells you what to do and you do it.

## Good to know with Antigravity

xSpeed Hub has no confirmation step of its own, and contact_support sends a real email when it runs. If you use the Turbo preset or a broad allow rule such as mcp(xspeedhub/*), nothing but the agent's own judgement stands between a prompt and that email, and the Hub's instruction to confirm is guidance, not a lock. An Ask or Deny rule for contact_support takes precedence over an Allow. For a pure diagnosis, send the connection token with Read-only everywhere on, or sign in as a Viewer member. Either refuses every write tool, and the diagnostic tools still work.

## More prompts for this job

They work in any client connected to xSpeed Hub.

- Using xSpeed Hub, why is the cache hit ratio so low on shop? Run the full health check and tell me the most likely cause.
- Using xSpeed Hub, is page caching actually working on blog? Benchmark cached against uncached and tell me if the second request was a hit.
- xSpeed Hub's get_health on docs shows a warning about the static-file rewrite. What does it mean and do I need to act?
- Use xSpeed Hub to check whether another caching plugin is conflicting with xSpeed on shop.
- Caching looks off on the staging site. Use xSpeed Hub to turn it on and tell me if the site refuses.
- Using xSpeed Hub, which Pro features would help the shop site, based on how it is set up now?
- With xSpeed Hub, compare the last few benchmark runs on blog and tell me whether my settings changes helped.

## Frequently asked questions

### Is BYPASS on cart and checkout a problem?

No. xSpeed excludes pages such as the cart, checkout and account by default, because a cached copy would be wrong for the next visitor. Antigravity can confirm that caching is healthy on the rest of the site through xSpeed Hub.

### Can Antigravity see why one specific URL bypasses the cache?

Not from the Hub tools alone. They report site-wide status, health checks and a benchmark of the home page. For one URL you need its response headers, and the reason header only appears when WP_DEBUG is on.

### Why are my WordPress pages not being cached?

The common causes are that page caching is switched off, the advanced-cache.php drop-in or the WP_CACHE constant in wp-config.php is missing, another caching plugin owns the drop-in, or the pages set cookies or headers that make them uncacheable. An agent can read all of these from get_health through xSpeed Hub and tell you which one applies to your site.

### What is the difference between get_cache_status and get_health?

get_cache_status is a quick summary: whether caching is on, the stats and the detected web server. get_health is the diagnostic. It adds the environment checks with pass or warn tones, 24 hourly hit and miss buckets and a 30-day hit-ratio series. The Hub tells the agent to use get_health when you are troubleshooting.

### Does run_benchmark give me a PageSpeed score?

No. run_benchmark measures how fast your own cache answers compared with an uncached request for the home page. For a Lighthouse score, ask for a speed test or a speed scan instead.

### Can the agent check every site at once?

Only partly. run_benchmark accepts every site in one call. get_cache_status and get_health take one site per call, and get_health does not accept site: "all", so for a fleet the agent calls them site by site or you use the Hub dashboard for the rollup.

### Will troubleshooting change anything on my site?

Not with the diagnostic tools. They are read tools and change nothing. Changes only happen if the agent calls a write tool such as toggle_cache, which runs once your connection allows writes, so your AI client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates.

## Find out why pages are not cached with other agents

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

## More with Antigravity

- [Purge the WordPress cache with Antigravity](https://xspeedcache.com/agent/antigravity/purge-cache/)
- [Scan a website for speed problems with Antigravity](https://xspeedcache.com/agent/antigravity/speed-scan/)
- [Run and track PageSpeed tests with Antigravity](https://xspeedcache.com/agent/antigravity/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Antigravity](https://xspeedcache.com/agent/antigravity/optimize-site/)
- [Tune WordPress cache settings with Antigravity](https://xspeedcache.com/agent/antigravity/cache-settings/)
- [Warm the WordPress cache with Antigravity](https://xspeedcache.com/agent/antigravity/preload-cache/)
- [Set up the Redis object cache with Antigravity](https://xspeedcache.com/agent/antigravity/object-cache/)
- [Manage Cloudflare caching with Antigravity](https://xspeedcache.com/agent/antigravity/cloudflare/)
- [Manage every WordPress site at once with Antigravity](https://xspeedcache.com/agent/antigravity/fleet/)

## Documentation

- How to read your cache diagnostics: https://xspeedcache.com/docs/cache-diagnostics/
- Understanding cache hits and misses: https://xspeedcache.com/docs/hits-and-misses/
- How to check your site health: https://xspeedcache.com/docs/health/
- Common problems and troubleshooting: https://xspeedcache.com/docs/common-problems-and-troubleshooting/
- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/