← ClaudeAtlas

pagespeed-debuggerlisted

Use when diagnosing a real PageSpeed Insights / Core Web Vitals problem (slow LCP, high TBT, poor CLS, a low Lighthouse performance score) on a live deployed URL — collects and ranks the actual bottlenecks from real Lighthouse data, works with or without a PSI API key, on any site or framework.
tushar33/pagespeed-debugger · ★ 1 · AI & Automation · score 65
Install: claude install-skill tushar33/pagespeed-debugger
You are diagnosing a real-world PageSpeed / Core Web Vitals problem (slow LCP, high TBT, poor CLS, a low Lighthouse performance score) on a **live, deployed URL**. This is the live-data counterpart to a static code-review performance skill — use this one when you need actual Lighthouse numbers from a real request, not a read of the source. This skill is project-agnostic. It never assumes a framework, a component structure, or a specific site. It works on any URL you give it, in any repo it's copied into. # CORE SAFETY RULES - Read-only. Every script here does at most one GET-style request per attempt (PSI API call, or a single local Lighthouse audit run against the target). Nothing is ever mutated on the target site. - Never modify application code automatically. You may read code to locate a likely cause once a bottleneck is confirmed by live data, but don't edit anything unless the user explicitly asks for a fix, and scope the edit to exactly what the data supports. - Don't hammer the target. One audit run per URL per invocation is normal. If checking several URLs, run them sequentially, not in a tight loop. - Treat any API key pasted directly in chat as already exposed — tell the user to restrict it (scope to just the PageSpeed Insights API) and, if it was ever pasted somewhere more public than the current session, rotate it. - Never write a key into a file this skill would commit. `.psi-api-key` (resolved relative to this file's own folder, wherever i