{
"markdown": "# PageSpeed Insights MCP Server\n\n[](https://ruslanlap.github.io/ruslanlap_buymeacoffe/)\n\n**Six-tool MCP server** for Google PageSpeed Insights & Chrome UX Report APIs. Analyze, compare, and optimize web performance directly through Claude, Cursor, or any MCP-compatible AI client.\n\n## โก Quick Start (Copy & Paste)\n\n```json\n{\n \"mcpServers\": {\n \"pagespeed-insights\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"pagespeed-insights-mcp\"],\n \"env\": { \"GOOGLE_API_KEY\": \"your-google-api-key\" }\n }\n }\n}\n```\n\nGet a free API key at [Google Cloud Console](https://developers.google.com/speed/docs/insights/v5/get-started) โ paste into Claude Desktop's `claude_desktop_config.json` โ restart. Done. ([Codex/OpenAI config](#codex--openai), [Docker](#option-3-docker))\n\n[](https://www.npmjs.com/package/pagespeed-insights-mcp)\n[](https://www.npmjs.com/package/pagespeed-insights-mcp)\n[](https://mcptoplist.com/server/io.github.ruslanlap%2Fpagespeed-insights-mcp)\n[](https://glama.ai/mcp/servers/ruslanlap/pagespeed-insights-mcp)\n\n
\n \n \n
\n\n[](https://github.com/ruslanlap/pagespeed-insights-mcp/pkgs/npm/pagespeed-insights-mcp)\n[](https://github.com/ruslanlap/pagespeed-insights-mcp/actions/workflows/ci.yml)\n[](https://ruslanlap.github.io/pagespeed-insights-mcp/)\n[](https://ruslanlap.github.io/pagespeed-insights-mcp/demo/)\n[](https://opensource.org/licenses/Apache-2.0)\n\n## ๐ฅ What Makes It Different\n\nMost PageSpeed MCP servers wrap **one** tool: \"run PSI on a URL.\" This server ships **six workflow tools** covering the full performance workflow โ not just a score, but an action plan:\n\n- **Full toolkit**: page analysis, CrUX real-user data (URL + origin), Lighthouse audits, multi-page & batch comparison, baselines, and regression tracking\n- **Deep diagnostics**: element-level, network, JavaScript, image optimization, render-blocking, and third-party impact analysis\n- **Actionable output**: a recommendations engine that turns raw Lighthouse data into prioritized fixes, plus visual analysis of screenshots\n- **Practical extras**: caching for repeat runs and smart recommendations tuned for AI agents to act on\n- **Battle-tested**: published on npm, listed in the [Official MCP Registry](https://registry.modelcontextprotocol.io/) and [Glama](https://glama.ai/mcp/servers), CI-tested with Vitest\n\n> **๐ฌ [View Interactive Demo โ](https://ruslanlap.github.io/pagespeed-insights-mcp/demo/)** โ See the tools in action with animated examples\n> Fallback URL: [https://ruslanlap.github.io/pagespeed-insights-mcp/demo.html](https://ruslanlap.github.io/pagespeed-insights-mcp/demo.html)\n\n## ๐ Table of Contents\n\n- [โก Quick Start (Copy & Paste)](#-quick-start-copy--paste)\n- [๐ฅ What Makes It Different](#-what-makes-it-different)\n- [โ๏ธ Client Configuration](#-client-configuration)\n- [๐ Example Output](#-example-output)\n- [๐ Documentation](#-documentation)\n- [๐ Release Notes](#-release-notes)\n- [๐ฏ Why You Need This](#-why-you-need-this)\n- [โจ Features](#-features)\n- [๐ Quick Installation](#-quick-installation)\n- [๐ Getting Google API Key](#-getting-google-api-key)\n- [โ๏ธ Claude Desktop Configuration](#-claude-desktop-configuration)\n- [๐ป Usage](#-usage)\n- [Available Tools](#available-tools)\n- [Development](#development)\n- [Troubleshooting](#troubleshooting)\n- [Requirements](#requirements)\n- [Security](#security)\n- [Acknowledgments](#acknowledgments)\n- [License](#license)\n- [Support](#support)\n\n## โ๏ธ Client Configuration\n\n### Claude Desktop\n\nAdd to your `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"pagespeed-insights\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"-p\", \"pino-pretty\", \"-p\", \"pagespeed-insights-mcp\", \"pagespeed-insights-mcp\"],\n \"env\": {\n \"GOOGLE_API_KEY\": \"your-google-api-key-here\"\n }\n }\n }\n}\n```\n\n### Codex / OpenAI\n\nAdd to your configuration (TOML):\n\n```toml\n[mcp_servers.pagespeed-insights]\ncommand = \"npx\"\nargs = [\n \"-y\",\n \"-p\",\n \"pino-pretty\",\n \"-p\",\n \"pagespeed-insights-mcp\",\n \"pagespeed-insights-mcp\"\n]\nenv = { GOOGLE_API_KEY = \"your-google-api-key-here\" }\n```\n\n> **Note:** The `pino-pretty` package is required for proper log formatting. The above configurations ensure it is installed automatically via `npx`.\n\n### For Grok Build (config.toml)\n\nAdd to `~/.grok/config.toml` (global) or `/.grok/config.toml` (project-scoped, higher priority):\n\n```toml\n[mcp_servers.pagespeed-insights]\ncommand = \"npx\"\nargs = [\"-y\", \"-p\", \"pino-pretty\", \"-p\", \"pagespeed-insights-mcp\", \"pagespeed-insights-mcp\"]\nenv = { GOOGLE_API_KEY = \"${GOOGLE_API_KEY}\" }\nenabled = true\n\n# Recommended companion professional MCPs (add once):\n# [mcp_servers.github] โ PRs, issues, code search\n# [mcp_servers.context7] โ fresh library docs (Upstash)\n# [mcp_servers.serena] โ semantic code intelligence (uses your .serena/ if present)\n```\n\n**Project-scoped example** (put in this repo's `.grok/config.toml` for local `dist/index.js` + tighter Serena):\n\n```toml\n[mcp_servers.pagespeed-insights]\ncommand = \"node\"\nargs = [\"/home/ubuntuvm/Projects/pagespeed-insights-mcp/dist/index.js\"]\nenv = { GOOGLE_API_KEY = \"${GOOGLE_API_KEY}\", NODE_ENV = \"development\" }\n```\n\nVerification inside Grok session:\n- `/mcps` (or Ctrl+L โ MCP tab) โ ensure pagespeed-insights shows \"running\"\n- Use tools: `pagespeed-insights__pagespeed_analyze_page`, `pagespeed-insights__pagespeed_get_field_data`, etc. (namespaced)\n\n## ๐ Example Output\n\nReal `pagespeed_analyze_page` results for **github.com** โ one mobile Lighthouse run. CrUX numbers come from `pagespeed_get_field_data` with `scope: \"origin\"`:\n\n**Lighthouse lab scores:**\n\n| Category | Score | Status |\n|---|---|---|\n| **Performance (mobile)** | **54/100** | ๐ด Poor |\n| **Performance (desktop)** | **52/100** | ๐ด Poor |\n\n**Core metrics (mobile):**\n\n| Metric | Value | Rating |\n|---|---|---|\n| First Contentful Paint | 11.9 s | ๐ด Poor |\n| Largest Contentful Paint | 13.4 s | ๐ด Poor |\n| Total Blocking Time | 30 ms | ๐ข Excellent |\n| Cumulative Layout Shift | 0.07 | ๐ข Good |\n| Speed Index | 11.9 s | ๐ด Poor |\n\n**CrUX field data โ real users, github.com origin (phone):**\n\n| Metric | p75 (real users) |\n|---|---|\n| First Contentful Paint | 1.9 s |\n| Largest Contentful Paint | 2.2 s |\n| Interaction to Next Paint | 243 ms |\n| Cumulative Layout Shift | 0.02 |\n\n> Results vary between runs โ Lighthouse lab data is noisy (a single run is one sample). Use `runs: 3-5` for medians.\n>\n> Lab vs field: Lighthouse throttles the connection (hence 54/100 mobile), while CrUX shows how actual GitHub visitors experience it โ both views come straight from this server's tools.\n\n## ๐ Documentation\n\nWe have comprehensive documentation available online.\n\n[**๐ View Full Documentation Site**](https://ruslanlap.github.io/pagespeed-insights-mcp/)\n\n- [๐ **Getting Started**](https://ruslanlap.github.io/pagespeed-insights-mcp/getting-started/)\n- [๐ ๏ธ **Tools Reference**](https://ruslanlap.github.io/pagespeed-insights-mcp/features/tools/)\n- [๐๏ธ **Architecture**](https://ruslanlap.github.io/pagespeed-insights-mcp/developers/architecture/)\n\n> You can also view the raw markdown files in the `docs/` directory or run `mkdocs serve` locally.\n\n## ๐ Release Notes\n\nCurrent release: **v2.0.0**.\n\nRecent highlights:\n\n- **v2.0.0** โ six workflow-oriented `pagespeed_*` tools replace the 19 v1 endpoint-shaped tools; all data tools support Markdown or JSON with structured results.\n\n> The badges at the top of this README update **automatically** on every release (npm version, GitHub package version, downloads). No manual edits needed.\n\nFor the complete release history, see [`CHANGELOG.md`](./CHANGELOG.md).\n\n## ๐ฏ Why You Need This\n\n**Pain point 1 โ \"My page is slow but I don't know why.\"**\nYou open PageSpeed Insights, get a wall of data, and still can't tell what to fix first. This MCP gives your AI assistant six focused workflows that cut through the noise: it identifies the exact render-blocking resources, the specific images wasting 2 MB, the third-party scripts eating 1.5 s of main-thread time โ and ranks them by impact. Ask \"why is my site slow?\" and get a prioritized fix list, not a 40-metric dashboard.\n\n**Pain point 2 โ \"I ship performance regressions to production.\"**\nYour team moves fast, deploys daily, and nobody runs a full Lighthouse audit before each merge. By the time someone notices the Core Web Vitals dropped, the regression is already live. This MCP lets any developer paste a URL into Claude/Cursor and get a complete audit โ lab data, field data from real Chrome users (CrUX), element-level CLS/LCP debugging โ in seconds. It's the difference between catching a regression at your desk and discovering it in a Slack message from the SEO team three days later.\n\n## โจ Features\n\n### Core Features\n\n- ๐ **Performance Analysis** of web pages using Google PageSpeed Insights\n- ๐ฑ **Multi-platform Support**: mobile and desktop devices\n- ๐ **Detailed Lighthouse Reports** with comprehensive metrics\n- ๐ **Simplified Reports** with key performance indicators\n- ๐ฏ **Smart Recommendations** with priority scoring and actionable fixes\n- ๐พ **Intelligent Caching** to reduce API calls and improve performance\n- ๐ **Localization** - support for multiple languages\n- โก **Quick Installation** - one command setup\n- ๐ณ **Docker Support** for containerized deployment\n\n### Advanced Analysis Tools (New!)\n\n- ๐ธ **Visual Analysis** - Screenshots, filmstrip, and full-page captures\n- ๐ฏ **Element-Level Debugging** - Find specific DOM elements causing issues\n- ๐ **Network Waterfall** - Detailed request timing and resource loading\n- โก **JavaScript Profiling** - Execution breakdown and unused code detection\n- ๐ผ๏ธ **Image Optimization** - Specific image issues with exact savings\n- ๐ซ **Render-Blocking Analysis** - Critical request chains and dependencies\n- ๐ **Third-Party Impact** - Script impact grouped by provider\n- ๐ **Full Audits** - Complete Lighthouse audits for all categories\n\n## ๐ Quick Installation\n\n### Option 1: Automatic Installation (Recommended)\n\n```bash\n# Set environment variable\nexport GOOGLE_API_KEY=your-google-api-key\n```\n\n```bash\ncurl -sSL https://raw.githubusercontent.com/ruslanlap/pagespeed-insights-mcp/master/scripts/install.sh | bash\n```\n\nThe installer uses the public npm package (`pagespeed-insights-mcp`) by default. To install the scoped GitHub Packages build instead, configure GitHub Packages authentication first and run:\n\n```bash\ncurl -sSL https://raw.githubusercontent.com/ruslanlap/pagespeed-insights-mcp/master/scripts/install.sh | \\\n PAGESPEED_INSIGHTS_MCP_PACKAGE=@ruslanlap/pagespeed-insights-mcp bash\n```\n\n### Option 2: Via npm or GitHub Packages\n\n#### From npm (Public Registry)\n\n```bash\n# Global installation from npm\nnpm install -g pagespeed-insights-mcp\n\n# Or use without installation\nnpx pagespeed-insights-mcp\n```\n\n#### From GitHub Packages\n\n```bash\n# First configure authentication (see GITHUB_PACKAGES.md for details)\n# Then install globally\nnpm install -g @ruslanlap/pagespeed-insights-mcp\n```\n\n> **Note:** This package is available on both npm and GitHub Packages.\n>\n> - For npm: Use `npm install pagespeed-insights-mcp`\n> - For GitHub Packages: Use `npm install @ruslanlap/pagespeed-insights-mcp` (requires GitHub authentication)\n>\n> For detailed instructions on installing from GitHub Packages, see [GITHUB_PACKAGES.md](GITHUB_PACKAGES.md) or visit the [GitHub Packages page](https://github.com/ruslanlap/pagespeed-insights-mcp/pkgs/npm/pagespeed-insights-mcp)\n\n### ๐ง Configuration\n\nThe MCP server requires a Google API key to access the PageSpeed Insights API.\n\n```bash\n# Set environment variable\nexport GOOGLE_API_KEY=your-google-api-key\n\n# Windows\n$env:GOOGLE_API_KEY=\"your-google-api-key\"\n\n# Or pass directly when running\nGOOGLE_API_KEY=your-google-api-key npx pagespeed-insights-mcp\n```\n\n### ๐ MCP Configuration Examples\n\n#### For Claude Desktop (with pino-pretty logging):\n\n```json\n\"pagespeed-insights\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"-p\",\n \"pino-pretty\",\n \"-p\",\n \"pagespeed-insights-mcp\",\n \"pagespeed-insights-mcp\"\n ],\n \"env\": {\n \"GOOGLE_API_KEY\": \"your-google-api-key-here\"\n }\n}\n```\n\n#### For Codex (with pino-pretty logging):\n\n```toml\n[mcp_servers.pagespeed-insights]\ncommand = \"npx\"\nargs = [\n \"-y\",\n \"-p\",\n \"pino-pretty\",\n \"-p\",\n \"pagespeed-insights-mcp\",\n \"pagespeed-insights-mcp\"\n]\nenv = { GOOGLE_API_KEY = \"your-google-api-key-here\" }\n```\n\n> **Note:** These examples include `pino-pretty` for better log formatting. For production use without pretty logs, see the [Logging section](#logging--pino-pretty-in-mcp-environments) below.\n\n### Google Antigravity\n\nExample configuration files are available in the [examples](./examples/) directory.\n\n### Option 3: Docker\n\n```bash\ndocker build -t pagespeed-insights-mcp .\ndocker run -e GOOGLE_API_KEY=your-key pagespeed-insights-mcp\n```\n\n## ๐ Getting Google API Key\n\nTo use this MCP server, you need a Google API key with the PageSpeed Insights API enabled.\n\n> [!TIP]\n> **โก Quick Setup Link:** You can go directly to the **[Google Cloud Credentials Setup Page](https://console.cloud.google.com/apis/credentials/key/)** to quickly create a key in your project.\n\n### Step-by-Step Guide\n\n1. Go to the [Google Cloud Console](https://console.cloud.google.com/) (or use the [Quick Setup Link](https://console.cloud.google.com/apis/credentials/key/)).\n2. Create a new project or select an existing one.\n3. Enable **PageSpeed Insights API**:\n - Navigate to **APIs & Services** โ **Library**.\n - Search for **\"PageSpeed Insights API\"** and click **Enable**.\n4. Create an API key:\n - Go to **APIs & Services** โ **Credentials**.\n - Click **Create Credentials** โ **API Key**.\n - Copy the generated key and set it as `GOOGLE_API_KEY` in your configuration.\n\n
\n \n
\n\n\n## โ๏ธ Claude Desktop Configuration\n\nConfig paths: **macOS** `~/Library/Application Support/Claude/claude_desktop_config.json` ยท **Windows** `%APPDATA%\\Claude\\claude_desktop_config.json` ยท **Linux** `~/.config/claude/claude_desktop_config.json` โ see [โ๏ธ Client Configuration](#๏ธ-client-configuration) above for the JSON. **Restart Claude Desktop** after editing.\n\n## ๐ป Usage\n\nAfter configuration, simply ask Claude any of these commands:\n\n### ๐ Full page analysis\n\n```\nAnalyze the performance of https://example.com\n```\n\n### ๐ฑ Mobile device analysis\n\n```\nAnalyze https://example.com for mobile devices with all categories\n```\n\n### โก Quick performance overview\n\n```\nGet a quick performance report for https://example.com\n```\n\n### ๐ฅ๏ธ Desktop analysis\n\n```\nAnalyze https://example.com performance for desktop devices\n```\n\n### ๐ Multi-category analysis\n\n```\nPerform a full audit of https://example.com including SEO, accessibility, and best practices\n```\n\n### ๐ฏ Smart performance recommendations\n\n```\nGet smart recommendations for improving https://example.com performance\n```\n\n### ๐พ Cache management\n\n```\nClear the cache to get fresh data for all subsequent requests\n```\n\n### ๐ธ Visual analysis\n\n```\nGet visual analysis for https://example.com showing screenshots and loading timeline\n```\n\n### ๐ฏ Element-level debugging\n\n```\nShow me which specific elements are causing performance issues on https://example.com\n```\n\n### ๐ Network waterfall analysis\n\n```\nAnalyze the network requests and resource loading for https://example.com\n```\n\n### โก JavaScript performance\n\n```\nGet JavaScript execution breakdown for https://example.com\n```\n\n### ๐ผ๏ธ Image optimization opportunities\n\n```\nShow me which images need optimization on https://example.com\n```\n\n### ๐ซ Render-blocking resources\n\n```\nFind render-blocking resources on https://example.com\n```\n\n### ๐ Third-party script impact\n\n```\nAnalyze third-party script impact on https://example.com performance\n```\n\n### ๐ Full Lighthouse audit\n\n```\nRun a full audit including accessibility, SEO, and best practices for https://example.com\n```\n\n## Available Tools (v2)\n\nVersion 2 replaces the former 19 endpoint-shaped tools with six workflow tools. This is a **breaking change**: update MCP client prompts, saved tool calls, and integrations to use the names below. Every data-returning tool accepts `responseFormat` (`markdown`, default, or `json`) and returns MCP `structuredContent`.\n\n| Tool | Use it for |\n|---|---|\n| `pagespeed_analyze_page` | One-page Lighthouse health check, full report, recommendations, audit findings, or a Mermaid map (`report`). |\n| `pagespeed_diagnose_page` | One focused investigation: `visual`, `elements`, `network`, `javascript`, `images`, `render-blocking`, or `third-parties`. |\n| `pagespeed_get_field_data` | CrUX real-user Core Web Vitals for a `page` or `origin`. |\n| `pagespeed_compare_pages` | Compare two pages now, or compare one page with its saved baseline (`mode`). |\n| `pagespeed_analyze_batch` | Triage 1โ10 pages with progress notifications when supported. |\n| `pagespeed_clear_cache` | Clear this process's in-memory API cache after a deploy. |\n\n### Migration from v1\n\n| v1 tools | v2 replacement |\n|---|---|\n| `analyze_page_speed`, `get_performance_summary`, `get_recommendations`, `get_full_audit`, `get_performance_map` | `pagespeed_analyze_page` with `report=full`, `summary`, `recommendations`, `audit`, or `performance-map` |\n| `get_visual_analysis`, `get_element_analysis`, `get_network_analysis`, `get_javascript_analysis`, `get_image_optimization_details`, `get_render_blocking_details`, `get_third_party_impact` | `pagespeed_diagnose_page` with the matching `focus` |\n| `crux_summary`, `get_origin_crux` | `pagespeed_get_field_data` with `scope=page` or `origin` |\n| `compare_pages`, `compare_baseline` | `pagespeed_compare_pages` with `mode=pages` or `baseline` |\n| `batch_analyze`, `clear_cache` | `pagespeed_analyze_batch`, `pagespeed_clear_cache` |\n| `full_report` | Run `pagespeed_analyze_page` and `pagespeed_get_field_data`; lab and field data stay explicit rather than being mixed. |\n\n### Examples\n\n```json\n{\"url\":\"https://example.com\",\"strategy\":\"mobile\",\"report\":\"recommendations\",\"responseFormat\":\"markdown\"}\n```\n\n```json\n{\"url\":\"https://example.com\",\"focus\":\"render-blocking\",\"responseFormat\":\"json\"}\n```\n\n```json\n{\"mode\":\"baseline\",\"url\":\"https://example.com\",\"strategy\":\"mobile\",\"runs\":3}\n```\n\n### Example\n\nanswer example from Claude Desktop with pagespeed-insights-mcp ๐ฅ๐ฅ๐ฅ\n\n## Development\n\nFor better log formatting during development, it is recommended to install `pino-pretty` globally:\n\n```bash\nnpm install -g pino-pretty\n```\n\n```bash\n# Development mode\nnpm run dev\n\n# Build project\nnpm run build\n\n# Run built server\nnpm start\n```\n\n### Logging / `pino-pretty` in MCP environments\n\nThis MCP server uses `pino` for logging and enables the `pino-pretty` transport when `NODE_ENV=development`.\n\n- If you **just want it to work with minimal setup** (Claude, Codex, etc.), set:\n\n```bash\nNODE_ENV=production GOOGLE_API_KEY=your-google-api-key npx pagespeed-insights-mcp\n```\n\nor in your MCP config:\n\n```jsonc\n\"pagespeed-insights\": {\n \"command\": \"npx\",\n \"args\": [\"pagespeed-insights-mcp\"],\n \"env\": {\n \"GOOGLE_API_KEY\": \"your-google-api-key-here\",\n \"NODE_ENV\": \"production\"\n }\n}\n```\n\n- If you **want pretty logs in development via `npx`**, you can have `npx` install `pino-pretty` alongside the server:\n\n```jsonc\n\"pagespeed-insights\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"-p\",\n \"pino-pretty\",\n \"-p\",\n \"pagespeed-insights-mcp\",\n \"pagespeed-insights-mcp\"\n ],\n \"env\": {\n \"GOOGLE_API_KEY\": \"your-google-api-key-here\"\n }\n}\n```\n\n## Troubleshooting\n\n### \"Google API key not provided\"\n\nEnsure the `GOOGLE_API_KEY` environment variable is set in your Claude Desktop configuration.\n\n### \"PageSpeed Insights API error: 403\"\n\nCheck if PageSpeed Insights API is enabled in your Google Cloud project.\n\n### \"Invalid URL\"\n\nEnsure the URL includes the protocol โ only `http://` and `https://` are accepted. Other schemes (`file://`, `ftp://`, `javascript:`, etc.) are rejected at the schema level.\n\n## Requirements\n\n- Node.js **20.19.0 or later** (Node 18 is EOL since April 2025 and is no longer supported).\n- A Google API key with PageSpeed Insights and (optionally) Chrome UX Report APIs enabled.\n\n## Security\n\nPlease report security issues privately โ do **not** open a public issue. See [SECURITY.md](./SECURITY.md) for the disclosure policy and operator hardening notes.\n\n## Acknowledgments\n\nSpecial thanks to [@engmsaleh](https://github.com/engmsaleh) (Mohamed Saleh Zaied) for his significant contribution to the development of this project.\n\nA very special thank you to [@system-conf](https://github.com/system-conf) for their outstanding and invaluable contribution to the growth and development of this project. Your dedication, expertise, and continuous support have made a tremendous impact โ this project wouldn't be where it is today without you. ๐\n\n## License\n\nApache-2.0 โ see [LICENSE](./LICENSE). Patents granted by contributors under the Apache License 2.0.\n\n## Support\n\nFor bug reports or feature requests, please create an issue in the repository.\n",
"bytes": 22268,
"sha": "204def15ddd525fe70e4e25aee11804bc51e1fcf20d2f59d1436b6822a4c44ad",
"repo_slug": "ruslanlap/pagespeed-insights-mcp",
"fonte": "repo",
"truncated": false,
"api": "https://agentalog.com/api/listings/mcp_io_github_ruslanlap_pagespeed_insights_m_8a0f5f64/readme"
}
![\"PageSpeed](\"https://raw.githubusercontent.com/ruslanlap/pagespeed-insights-mcp/master/assets/1.png\")
\n ![\"PageSpeed](\"https://raw.githubusercontent.com/ruslanlap/pagespeed-insights-mcp/master/assets/2.png\")
\n![\"Google](\"assets/3.png\")
\n