Pagespeed Insights MCP server

@pipeworx/pagespeed-insights

Google's PageSpeed Insights — runs Lighthouse against any public URL on Google's own infrastructure and returns the performance/accessibility/best-practices/SEO scores, the lab timing metrics behind them, and the ranked list of specific fixes with the milliseconds or bytes each would save; plus the real-user Chrome UX Report data for that page and its origin.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

the lab run and its ranked opportunities.

• pagespeedaudit(url, strategy?, categories?, maxopportunities?, locale?) —

page and its origin, with Google's pass/fail verdict.

• pagespeedfieldmetrics(url, strategy?) — real-user Core Web Vitals for the

Auth

BYO with platform fallback: apiKey, or PLATFORMGOOGLEAPIKEY when that secret is set on the gateway.

The documented keyless path exists but is unusable. Unkeyed requests are billed to a single shared Google anonymous consumer project whose daily quota is exhausted — three consecutive unkeyed calls returned HTTP 429, "Quota exceeded … for consumer 'project_number:583797351490'" (verified live 2026-09-17). That project number is the same for every anonymous caller on the internet, so the quota is not ours to nurse and retrying does not help. The pack tries keyless first and refuses with wording that says a key is required.

A key is free, instant and needs no billing account: create one at and enable the PageSpeed Insights API at . Quota is 25,000 requests/day, 240/minute. The same key serves the chrome-ux-report pack.

Relationship to the chrome-ux-report pack

chrome-ux-report reports what real visitors experienced; it cannot tell you why, because field data carries no diagnostics. This pack runs the page and names the causes. Use crux for "is this site fast for real users", use this for "what specifically is making it slow, and what do I fix first".

Data sources

• https://www.googleapis.com/pagespeedonline/v5/runPagespeed

Traps, verified live 2026-09-17

passes an explicit 60s budget; a caller batching ten URLs should expect minutes.

• A call takes 10–40 seconds. Google actually loads the page. The pack

load on a throttled emulated phone from a Google data centre; the field block is 28 days of real visits on real devices. A 95 lab score with failing field CWV means real users are on worse hardware than the emulation — and it is the field number Search uses. Both are returned, labelled, never blended.

• Lab and field disagree routinely and both are right. The lab run is one

and for a low-traffic URL Google populates the page block with the origin's numbers and sets originfallback: true. Reading that as page data attributes the whole site's performance to one URL. Reported here as isorigin_fallback.

• loadingExperience is the page, originLoadingExperience is the site —

that errored returns null, not zero.

• Category scores are 0–1 floats, not 0–100, and are nullable. A category

the useful part buried in error.errors[].reason. "Bad request" here often means "your site returned a 500 to Google's crawler".

• An unreachable target is an HTTP 400 from Google, not a 404 or 5xx, with

returns the same metric as a decimal string. The pack normalises to the decimal.

• CLS in this API is an integer ×100 (5 means 0.05), while the CrUX API

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "pagespeed-insights": {
      "url": "https://gateway.pipeworx.io/pagespeed-insights/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.