analyze_resources
Analyze website resources (images, JS, CSS, fonts) for optimization opportunities
LABSCO SUMMARY
Lighthouse, but the results come back typed.
The structuredContent guarantee is what makes this useful to an agent rather than just runnable: every tool has an outputSchema, so a score or a set of opportunities arrives as typed data the model can reason over instead of a JSON blob to re-parse. The focused tools matter too — get_lcp_opportunities and find_unused_javascript go straight to the fix rather than making you read a full report to find it.
What it is
A server that runs Google Lighthouse audits: 12 tools covering the full audit plus focused scores for performance, accessibility, SEO, PWA readiness and security, Core Web Vitals, resource analysis and performance budgets. Every tool returns validated structuredContent against an outputSchema.
What you get
- run_audit runs a comprehensive Lighthouse audit, and the focused tools return one dimension each: get_performance_score, get_accessibility_score with recommendations, get_seo_analysis, check_pwa_readiness and get_security_audit for HTTPS, CSP and other measures
- get_core_web_vitals reports LCP, INP and CLS, and check_performance_budget tests a site against thresholds you specify
- compare_mobile_desktop runs the audit on both and compares, with throttling, so you see how a page behaves on each
- Optimization opportunities called out directly: get_lcp_opportunities for what is slowing the largest paint, find_unused_javascript to trim bundle size, and analyze_resources across images, JS, CSS and fonts
- Every tool declares an outputSchema and returns validated structuredContent, so a client gets typed data rather than a JSON string to parse
Requirements
Node.js 22.0.0 or newer and a Chrome/Chromium browser, which Lighthouse manages automatically. Run it as npx @danielsogl/lighthouse-mcp. No account.
Setup effort
One command — npx @danielsogl/lighthouse-mcp@latest
USE CASES
01
Auditing a page you just shipped
Run the full audit, then pull the performance and accessibility scores with their recommendations to see what regressed.
02
Chasing Core Web Vitals
Read LCP, INP and CLS, then get the specific LCP opportunities so you fix the largest paint rather than guessing at it.
03
Trimming the page weight
Find the unused JavaScript and analyze the images, CSS and fonts to see which resources are worth optimizing first.
04
Holding a page to a budget
Check the site against your performance thresholds and compare mobile against desktop, so a change has to clear the bar on both.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_performance_budget
Check if website performance meets specified budget thresholds
check_pwa_readiness
Check Progressive Web App readiness and requirements
compare_mobile_desktop
Compare website performance between mobile and desktop devices
find_unused_javascript
Find unused JavaScript code to reduce bundle size
get_accessibility_score
Get the accessibility score and recommendations for a website
get_core_web_vitals
Get Core Web Vitals metrics for a website
get_lcp_opportunities
Get LCP optimization opportunities for a website
get_performance_score
Get the performance score for a website
get_security_audit
Perform security audit checking HTTPS, CSP, and other security measures
get_seo_analysis
Get SEO analysis and recommendations for a website
run_audit
Run a comprehensive Lighthouse audit on a website
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected. check_pwa_readiness is missing from the documentation. The 8 prompts and 8 resources the server also ships are not tools.
Requires
- Node.js 22.0.0 or newer
- Chrome/Chromium browser (automatically managed by Lighthouse)
- VS Code, Cursor, Windsurf, Claude Desktop, or any other MCP client
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @danielsogl/lighthouse-mcp@latestMCP Clients
VS Code
VS CODE · TERMINAL
code --add-mcp '{"name":"lighthouse","command":"npx","args":["-y","@danielsogl/lighthouse-mcp@latest"]}'VS Code Insiders
VS CODE INSIDERS · TERMINAL
code-insiders --add-mcp '{"name":"lighthouse","command":"npx","args":["-y","@danielsogl/lighthouse-mcp@latest"]}'Cursor, Windsurf, Claude Desktop
JSON
{
"mcpServers": {
"lighthouse": {
"command": "npx",
"args": [
"@danielsogl/lighthouse-mcp@latest"
]
}
}
}
