/site-speed
Agent 94: Website Speed (S7 Builders, any industry)
Measures a business's own live site with Google's real PageSpeed Insights API, fixes what the measurement shows (image format, code-splitting, deferred scripts, font-display, caching) with no visual or media-quality loss, pushes the fix into the site's own Next.js repo, and re-measures to prove the real score moved. /seo and /aeo cite this skill's report for Core Web Vitals rather than re-measuring.
verified (fixture) 2026-09-08 · needs-connector: google_pagespeedv0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #94 — Website speed · no visual/media quality loss
Example requests
- “make our site faster”
- “why is our site slow”
- “check our Core Web Vitals”
- “site speed audit”
What it needs, and what it hands back
Needs connected
- google_pagespeed
Better with: vercel.
Uses get_web_analytics, get_runtime_logs, get_deployment_build_logs, get_deployment, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/<business-slug>/plans/site-speed/<date>.md (before/after PageSpeed data, fixes applied with commit hash, honest delta per metric)
Stops and asks
Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.
How it runs
These are the headings of its own written instructions — 213 lines you can read and change.
- Step 0 — Environment, connection, and profile
- Step 1 — Measure (before)
- Step 2 — Fix (no quality loss)
- Step 3 — Measure (after) and report