Pagespeed Insights MCP server

Read from the package source without running it. The installed server may list more.

• pagespeed_analyze_batch

  Analyze 1–10 public URLs and return per-page results plus success/failure counts. Use pagespeed_analyze_page for one URL or pagespeed_compare_pages for a direct comparison. Example: triage the ten highest-traffic landing pages. Progress notifications are emitted when supported by the client.

• pagespeed_analyze_pagewrite action

  Run a PageSpeed Insights Lighthouse analysis for one public page. Start with report=summary for a health check; choose full for audits, recommendations for a prioritized fix list, audit for non-performance categories, or performance-map for Mermaid. Example: analyze a mobile product page and return the three most useful remediation steps. Returns a report plus structured result. The Google API is

• pagespeed_clear_cache

  Clear only this server process's in-memory PageSpeed response cache, forcing later analysis calls to contact Google again. Use after a deploy when a cached result is stale. It does not change the target website, files, or remote data; repeating the call is safe.

• pagespeed_compare_pages

  Compare two pages now (mode=pages) or measure one page against its locally stored baseline (mode=baseline). Baseline mode records the first call; use runs=3 or more and rely on guaranteed deltas, not medians alone. Example: compare staging against production, or verify whether a deployed fix improved mobile LCP. replaceBaseline overwrites local baseline state.

• pagespeed_diagnose_page

  Inspect one page through exactly one diagnostic lens: visual, elements, network, javascript, images, render-blocking, or third-parties. Use after pagespeed_analyze_page identifies a problem; do not use it for a general score. Example: focus=render-blocking to identify CSS/JS delaying first render. Returns focused evidence rather than a full Lighthouse dump.

• pagespeed_get_field_data

  Get real-user Core Web Vitals from Chrome UX Report, not Lighthouse lab measurements. Use scope=page for one URL; use scope=origin with a bare origin when the page has insufficient traffic. Example: check mobile LCP and INP for https://example.com/checkout. Returns p75 field metrics or a clear no-data result.

• Code scan25 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 5 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Pagespeed Insights: common questions

Is Pagespeed Insights MCP server safe?

Mostly: it is graded B (83/100). Read the Pagespeed Insights safety report

How do I install Pagespeed Insights?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Pagespeed Insights need an API key?

Yes. The registry entry asks for GOOGLE_API_KEY.

Is Pagespeed Insights maintained?

The last commit was 5 days ago (2026-09-14). The latest release is v2.1.0.