MCP PageSpeed Insights
Provides detailed Lighthouse audits including performance metrics, accessibility issues, SEO scores, and optimization opportunities for web pages.
Allows analyzing web page performance, accessibility, SEO, and best practices using Google PageSpeed Insights API, providing full Lighthouse reports and prioritized recommendations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP PageSpeed InsightsAnalyze the performance of https://example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP PageSpeed Insights
An MCP (Model Context Protocol) server that connects LLMs to Google PageSpeed Insights. It lets AI assistants analyze any web page's performance, accessibility, SEO, and best practices — then help you act on the results.
Prerequisites
Node.js 18+
Google API Key — get one for free at Google Developers Console
Related MCP server: MCP Server Pagespeed
Setup
git clone https://github.com/NicolasET/mcp-pagespeed-insight.git
cd mcp-pagespeed-insight
npm install
npm run buildConfiguration
Add the server to your MCP client.
Claude Code (CLI)
claude mcp add pagespeed-insights -e GOOGLE_API_KEY=your_api_key_here -- node /absolute/path/to/mcp-pagespeed-insights/dist/server.jsOn Windows (outside WSL), wrap with cmd /c:
claude mcp add pagespeed-insights -e GOOGLE_API_KEY=your_api_key_here -- cmd /c node C:\absolute\path\to\mcp-pagespeed-insights\dist\server.jsScope options (add --scope before the server name):
Scope | Description |
| Private to you, current project only |
| Shared with the team via |
| Private to you, available across all projects |
Example with scope:
claude mcp add --scope user pagespeed-insights -e GOOGLE_API_KEY=your_api_key_here -- node /absolute/path/to/mcp-pagespeed-insights/dist/server.jsAfter adding, verify with:
claude mcp listClaude Desktop
Edit claude_desktop_config.json (Settings > Developer > Edit Config):
{
"mcpServers": {
"pagespeed-insights": {
"command": "node",
"args": ["/absolute/path/to/mcp-pagespeed-insights/dist/server.js"],
"env": {
"GOOGLE_API_KEY": "your_api_key_here"
}
}
}
}Other MCP clients (Cursor, Windsurf, etc.)
Refer to your client's docs for registering a stdio MCP server. The command is:
node /absolute/path/to/mcp-pagespeed-insights/dist/server.jsThe GOOGLE_API_KEY environment variable must be set.
Available Tools
Tool | Description |
| Full Lighthouse analysis — all category scores, key metrics, and top improvement opportunities |
| Core Web Vitals and performance scores (LCP, CLS, TBT, FCP, SI, TTI, TTFB) |
| Prioritized improvement opportunities sorted by estimated impact |
| Resource breakdown by type, transfer sizes, and largest resources |
| JavaScript boot-up time, main thread work, and unused code |
| Images needing compression, modern format conversion, or lazy-loading |
| Render-blocking CSS/JS, critical request chains, preconnect/preload opportunities |
| Third-party scripts by provider, size, blocking time, and facade opportunities |
| Accessibility score and all failing audits with affected elements |
| Side-by-side mobile vs desktop comparison of scores and metrics |
All tools accept a url parameter (required) and a strategy parameter (mobile or desktop, defaults to mobile). The analyze_url and compare_strategies tools also accept a categories array to select which Lighthouse categories to run.
Environment Variables
Variable | Required | Default | Description |
| Yes | — | Your Google API key for PageSpeed Insights |
| No |
| How long to cache API responses in milliseconds |
Example Usage
Once configured, you can ask your AI assistant things like:
"Analyze the performance of https://example.com"
"What are the biggest performance issues on my site and how can I fix them?"
"Compare mobile vs desktop performance for https://example.com"
"Which images on https://example.com need optimization?"
"Are there any accessibility issues on https://example.com?"
"What third-party scripts are slowing down https://example.com?"
Development
# Run in development mode (no build needed)
npm run dev
# Type-check without emitting
npm run typecheck
# Run tests
npm test
# Run tests in watch mode
npm run test:watch
# Build for production
npm run buildLicense
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NicolasET/mcp-pagespeed-insight'
If you have feedback or need assistance with the MCP directory API, please join our Discord server