Lighthouse-MD: PageSpeed audits to CLAUDE.md

Run a Lighthouse / PageSpeed Insights audit on any page, generate a CLAUDE.md fix plan for Claude Code.

Find out why a page is slow, then let Claude Code fix it. One click runs Google PageSpeed Insights on the current tab and turns the Lighthouse result into a CLAUDE.md fix plan. Raw Lighthouse JSON is too large and too flat for a coding agent. This extension keeps the structure the agent needs: what failed, which files cause it, how to fix it, and what must not break. HOW IT WORKS 1. Open the page and click the toolbar icon. Pick Mobile or Desktop. 2. Google runs the audit (10-30 seconds). You can close the popup. The result waits for you when you reopen it. 3. See the four Lighthouse scores: Performance, Accessibility, Best Practices, SEO. 4. Click "Ask Claude to fix problems" to open Claude Code with the fix plan loaded. Or download or copy the CLAUDE.md into any repo. You can also right-click any page and choose "Analyze this page with Lighthouse-MD". WHAT IS IN THE CLAUDE.MD - Every failing audit, with the measured value and the passing threshold - The offenders for each audit: the exact scripts, images, fonts, DOM nodes and third-party domains - A short, specific fix for each audit - Core Web Vitals and lab metrics: LCP, CLS, TBT, FCP, Speed Index - Third-party impact and main-thread time by category - Framework advice when Lighthouse detects your stack (WordPress, Next.js, React, Angular and others) - A "currently passing, do not regress" list, so the agent does not break accessibility while it fixes speed - The test setup: device, network throttling and CPU throttling FREE WEEKLY REPORT (OPTIONAL) After a result, enter your email to get that page's mobile score every week: Performance score, Core Web Vitals, the change since last week, and the top issues. One email a week. Unsubscribe in one click. Free for one page. WORKS WITH - Claude Code (desktop app and CLI) - Cursor, Windsurf, Aider and other AI coding tools that read an instructions file - Any public page that Google PageSpeed Insights can reach LIMITS - Public URLs only. Google runs the audit, so it cannot reach localhost or pages behind a login. For those, use Lighthouse in Chrome DevTools, or audit a public preview deploy. - Lab data only, not real-user (field) data. - One page at a time. No site crawl. PRIVACY - The extension reads only the URL of the active tab, and only when you click. - That URL goes to lighthouse-md.com and then to Google PageSpeed Insights for the audit. We keep it only if you sign up for the weekly report. - Your email leaves the browser only if you type it into the weekly report field. - We count anonymous events (audit started, audit finished) with no URL, email or ID attached. - No account. No ads. We never sell data. Full policy: lighthouse-md.com/privacy USE CASES - Fix a slow page: give Claude Code the brief and let it work through LCP, CLS and render-blocking issues - Check a release before launch: run it on a public preview deploy - Track one page over time with the weekly email - Learn Lighthouse: each failing audit comes with a plain-language fix you can study ALSO ON THE WEB The same tool runs at lighthouse-md.com with nothing to install. Each common audit also has a free fix guide at lighthouse-md.com/audits. FEEDBACK I read every review. If an audit gets a weak fix, name the audit ID in your review and I will improve it.