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
    167 npm
    12
    MIT

  • pagespeed-insights-mcp

    damijanc
    A
    license
    Not graded
    quality
    C
    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
    C
    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.
    6 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.4/5.0

Scored across 8 tools

Disambiguation3/5

Several tools cluster around the same PageSpeed analysis: report explicitly includes scores and failing findings, overlapping with check_pagespeed and diagnose_page, and diagnose/diagnose_page share a confusing prefix. The descriptions are detailed enough to mostly separate use cases, but the boundaries are not crisp.

Naming Consistency3/5

The set mixes verb_noun names like check_pagespeed, diagnose_page, explain_lcp, and check_status with bare verbs like report, compare, and diagnose, plus the noun phrase field_data. The snake_case style is consistent and readable, but there is no uniform action-object convention and the diagnose/diagnose_page pair is easy to confuse.

Tool Count5/5

Eight tools is well-scoped for a PageSpeed Insights server: core measurement, full reporting, focused diagnostics, field data, LCP explanation, before/after comparison, configuration checking, and job polling all fit. The count is neither bloated nor thin.

Completeness5/5

The surface covers the key workflows: measuring performance, diagnosing failing audits, retrieving real-user field data, explaining LCP, comparing changes, checking configuration, and collecting long-running jobs. There are no obvious dead ends or major missing operations for this domain.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources