get_image_optimization_details

MCP tool from Pagespeed Insights MCP by ruslanlap

Images needing optimization with exact savings

How to use it

get_image_optimization_details is exposed by the Pagespeed Insights MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the get_image_optimization_details tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Pagespeed Insights MCP

$npx pagespeed-insights-mcp

FULL PAGESPEED INSIGHTS MCP LISTING

Other tools in Pagespeed Insights MCP (26)

analyze_page_speed

Full Lighthouse analysis — all metrics and audits

Analyze up to 10 URLs in parallel with progress tracking

array of categories to audit (default: ["performance", "accessibility", "best-practices", "seo"])

array of categories ["performance", "accessibility", "best-practices", "seo", "pwa"]

Clear internal cache to force fresh API requests

Side-by-side performance comparison between two URLs

Real-world Core Web Vitals from Chrome UX Report (field data)

"PHONE", "DESKTOP", or "TABLET" (default: "PHONE")

Unified report combining Lighthouse lab data with CrUX field data

get_element_analysis

LCP/CLS DOM elements causing performance issues

Complete Lighthouse audit for all categories

get_javascript_analysis

JS bootup time, main-thread work, unused & duplicated modules

get_network_analysis

Network waterfall — all requests with timing and size

get_origin_crux

Domain-level (origin) Chrome UX Report field data across all pages

get_performance_map

Mermaid flowchart visualizing performance score, Core Web Vitals status, and top opportunities

get_performance_summary

Simplified key-metrics report

get_recommendations

Prioritized recommendations with actionable fixes

get_render_blocking_details

Render-blocking resources and critical request chains

get_third_party_impact

Third-party script impact grouped by provider

get_visual_analysis

Screenshots, filmstrip, and full-page captures

locale for results (default: "en")

"mobile" or "desktop" (default: "mobile")

(required): URL of the page to analyze

(required): First URL to compare

(required): Second URL to compare

(required): Array of URLs to analyze (max 10)