PageSpeed Insights MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Google API key for PageSpeed Insights API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_page_speedC | Run comprehensive Google PageSpeed Insights analysis with Lighthouse metrics |
| get_performance_summaryB | Get simplified performance metrics and opportunities for a webpage |
| crux_summaryB | Get Chrome User Experience Report real-world field data for Core Web Vitals |
| compare_pagesB | Compare performance metrics between two URLs side-by-side |
| full_reportC | Unified report combining Lighthouse lab data with CrUX field data |
| batch_analyzeC | Analyze performance for multiple URLs with progress tracking |
| clear_cacheA | Clear the internal cache to force fresh API requests |
| get_recommendationsC | Generate smart performance recommendations with priority scoring and actionable fixes |
| get_visual_analysisA | Get screenshots and visual timeline showing how the page loads (final screenshot, filmstrip frames, full-page screenshot) |
| get_element_analysisB | Get specific DOM elements causing performance issues (LCP element, CLS elements, lazy-loaded issues) |
| get_network_analysisB | Get detailed network waterfall showing all requests with timing, size, and priority |
| get_javascript_analysisA | Get JavaScript execution breakdown showing bootup time, unused code, and main thread work |
| get_image_optimization_detailsB | Get specific images needing optimization with exact savings potential |
| get_render_blocking_detailsC | Get render-blocking resources and critical request chains showing loading dependencies |
| get_third_party_impactC | Get third-party script impact analysis grouped by entity (Google, Facebook, etc.) |
| get_full_auditB | Get comprehensive audit results for all categories (performance, accessibility, SEO, best practices, PWA) |
| get_performance_mapC | Generate a Mermaid flowchart visualizing the performance score, Core Web Vitals status, and top optimization opportunities in a single visual map |
| get_origin_cruxA | Get Chrome UX Report field data for an entire origin (domain-level), aggregating real-user Core Web Vitals across all pages — useful when a single URL lacks enough traffic for page-level data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/ruslanlap/pagespeed-insights-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server