Back to all days

Day 19 — Performance Optimization

Core Web Vitals Monitor

Track LCP, CLS, and INP across every site you manage — with trends, budgets, alerts, and a prioritized hit list of what to fix first.

An MCP server that turns performance monitoring into a conversation. Ask which sites are failing, where metrics are regressing, and what optimizations would have the biggest impact. No more squinting at Lighthouse reports.

Example Queries

“Which sites are failing their Core Web Vitals?”
“Show me the LCP trend for Acme Store over the last 8 weeks”
“What are the top optimization opportunities ranked by impact?”
“Which resources on the store are render-blocking?”
“How big is the hero image on the homepage?”
“Is the dashboard INP getting better or worse?”

Tools

6 MCP Tools

ToolWhat It Does
site_lookupSearch monitored sites by name, category, or owner. Returns latest Core Web Vitals scores and overall health status.
vitals_snapshotGet the latest Core Web Vitals snapshot for a site — LCP, CLS, INP, FCP, TTFB — with pass/fail status against Google thresholds.
trend_analysisAnalyze Core Web Vitals trends over time. Weekly snapshots showing direction of change and whether metrics are improving or regressing.
budget_checkCheck performance budgets across all monitored sites. Shows which sites are passing, warning, or failing their thresholds.
optimization_hitlistGet prioritized optimization recommendations ranked by impact and effort. Includes estimated performance savings in milliseconds.
resource_auditAudit page resources — images, scripts, stylesheets, fonts — with sizes, load times, and whether they block rendering.

Monitored Sites

6 Sites Tracked

Acme Store

E-Commerce

warning
2800msLCP
0.07CLS
195msINP

Acme Blog

Content

passing
1370msLCP
0.01CLS
84msINP

Acme Dashboard

SaaS App

failing
1790msLCP
0.03CLS
370msINP

Acme Marketing

Marketing

warning
1840msLCP
0.13CLS
138msINP

Acme Docs

Documentation

passing
885msLCP
0.01CLS
56msINP

Acme Careers

Careers

passing
2450msLCP
0.03CLS
122msINP

Why This Build

Why Core Web Vitals?

Google uses Core Web Vitals as a ranking signal. Your hero image is 4.2MB and your CTO is wondering why bounce rate is 60%. The data is there — buried in Lighthouse reports nobody reads.

Most teams run a Lighthouse audit before launch, get a green score, and never look again. Then someone adds an unoptimized image, a third-party script starts blocking render, and performance degrades quietly until someone notices the SEO drop.

This server tracks six sites across eight weeks of measurements, with performance budgets, automated alerts, a prioritized optimization hit list, and full resource audits. Ask a question about your site's performance and get an answer backed by real data — not a vague Lighthouse score.

Demo Data

What's Inside

6

Sites Monitored

96

Measurements

18

Performance Budgets

15

Recommendations

8

Alerts

25

Resources Tracked

Six sites spanning e-commerce, content, SaaS, marketing, docs, and careers. Eight weeks of weekly Core Web Vitals measurements on both mobile and desktop. Performance budgets with Google's official thresholds. Realistic regressions (hero image bloat, heavy JS bundles, ad-slot layout shifts) and a prioritized optimization hit list with estimated savings.

Setup

Try It Locally

cd day19-core-web-vitals
npm install && npm run seed && npm run build

Then add the config to Claude Desktop and restart.

Need a performance monitoring setup that actually gets used?

If your Lighthouse scores are gathering dust and your Core Web Vitals are a mystery, let's talk about making performance data conversational.