For Lighthouse & PageSpeed Insights reports

Reports Markdown

Turn a Lighthouse export or a PageSpeed Insights result into clean Markdown, structured JSON, or a filtered, stack-aware AI prompt — ready to paste into Claude Code, Cursor, or ChatGPT.

Why this exists

  1. 01

    PageSpeed Insights has no export button.

    The web report at pagespeed.web.dev only lets you view results on screen or grab the raw JSON — there's no built-in way to turn a scan into something you can paste into a doc, ticket, or PR.

  2. 02

    A Lighthouse report can run to hundreds of audits and megabytes of nested JSON.

    Google's own Lighthouse team has discussed shipping a lighter "summary mode" because the full report is too heavy to work with directly. This tool parses it down to what's actually broken.

  3. 03

    Pasting a whole report into an AI chat wastes tokens and buries the real issues.

    The common workaround is select-all, copy, and dump an entire report into ChatGPT or Claude and hope it finds the problems. This tool filters to errors and warnings first, so the model gets a clean, focused brief instead of noise.

  4. 04

    Clients and PMs can't read a JSON blob.

    Non-engineers need a plain-English summary, not auditRefs — export clean Markdown they can drop straight into a status update or a GitHub issue.

Built for vibe coding

The AI-prompt export skips passed audits and boilerplate, keeps only real errors and warnings, and includes your tech stack — so pasting it into Claude Code, Cursor, or ChatGPT gets you a fix for your framework, not generic advice for a page it's never seen.