strategy
"mobile" or "desktop" (default: "mobile")
How to use it
Project documentation lists strategy for the Pagespeed Insights MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Pagespeed Insights MCP
npx pagespeed-insights-mcpOther tools in Pagespeed Insights MCP (30)
Full Lighthouse analysis — all metrics and audits
Analyze up to 10 URLs in parallel with progress tracking
array of categories to audit (default: ["performance", "accessibility", "best-practices", "seo"])
array of categories ["performance", "accessibility", "best-practices", "seo", "pwa"]
Clear internal cache to force fresh API requests
Side-by-side performance comparison between two URLs
Real-world Core Web Vitals from Chrome UX Report (field data)
"PHONE", "DESKTOP", or "TABLET" (default: "PHONE")
Run pagespeedanalyzepage and pagespeedgetfielddata; lab and field data stay explicit rather than being mixed.
LCP/CLS DOM elements causing performance issues
Complete Lighthouse audit for all categories
Images needing optimization with exact savings
JS bootup time, main-thread work, unused & duplicated modules
Network waterfall — all requests with timing and size
Domain-level (origin) Chrome UX Report field data across all pages
Mermaid flowchart visualizing performance score, Core Web Vitals status, and top opportunities
Simplified key-metrics report
Prioritized recommendations with actionable fixes
Render-blocking resources and critical request chains
Third-party script impact grouped by provider
Screenshots, filmstrip, and full-page captures
Triage 1–10 pages with progress notifications when supported.
One-page Lighthouse health check, full report, recommendations, audit findings, or a Mermaid map (report).
Clear this process's in-memory API cache after a deploy.
Compare two pages now, or compare one page with its saved baseline (mode).
One focused investigation: visual, elements, network, javascript, images, render-blocking, or third-parties.
CrUX real-user Core Web Vitals for a page or origin.
(required): First URL to compare
(required): Second URL to compare
(required): Array of URLs to analyze (max 10)