Skip to main content
Glama
Considus

pagespeed-insights-mcp

by Considus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pagespeed-insights-mcp

  • MCP Server Pagespeed

    enemyrr
    A
    license
    B
    quality
    D
    maintenance
    Enables AI models to analyze webpage performance using the Google PageSpeed Insights API, providing real-time performance scores and improvement suggestions.
    1
    131 npm
    11
    MIT

  • pagespeed-insights-mcp

    damijanc
    A
    license
    Not graded
    quality
    D
    maintenance
    This MCP server integrates Google PageSpeed Insights to analyze website performance, accessibility, best practices, SEO, and PWA on mobile and desktop, returning detailed audits and optimization opportunities.
    MIT

Related Servers

  • page-speed-insights-mcp

    Sivakumar-intoaec
    F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that wraps the Google PageSpeed Insights API to analyse web performance, providing tools for scores, Core Web Vitals, opportunities, diagnostics, and batch analysis.
    -

  • web-perf-mcp

    vigneshshanmugam
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that audits web pages using Lighthouse and Puppeteer to find performance bottlenecks and generate CPU profiles for optimization.
    2 npm
    MIT

  • crux-mcp

    miguelrisero
    A
    license
    A
    quality
    B
    maintenance
    MCP server for the Chrome UX Report, providing real-user Core Web Vitals (LCP, INP, CLS) and historical trends for any origin or URL via natural language queries.
    3
    2
    MIT

  • multi-site-monitor

    faisibash-oss
    A
    license
    Not graded
    quality
    B
    maintenance
    An MCP server that pulls PageSpeed Insights and Google Search Console data across multiple owned sites, enabling cross-site performance reports and synthesis via Claude.
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 6 tools

Disambiguation4/5

The tools are mostly distinct: lab measurement, CrUX field data, LCP phase diagnosis, baseline comparison, setup diagnostics, and async result retrieval each have a clear role. Some overlap remains because analyse_page can return field_data and explain_lcp also uses CrUX/LCP data, but the descriptions explicitly route between them.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_object pattern: get_job_result, check_setup, get_field_data, analyse_page, explain_lcp, compare_to_baseline. There is no mixed casing or conflicting verb style.

Tool Count5/5

Six tools is well scoped for a PageSpeed Insights server, covering setup, lab analysis, field data, LCP explanation, baseline comparison, and async job retrieval. No tool appears to be filler.

Completeness4/5

The surface covers the core PSI workflows: configuration check, lab measurement, real-user field data, LCP diagnosis, regression comparison, and job collection. Minor lifecycle gaps exist, such as no job cancellation/listing or baseline reset/delete, but agents can mostly work around them.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources