Frequently Asked Questions
Everything you need to know about PageSpeed Exporter, Lighthouse JSON reports, and using performance data with AI agents.
Why can't I just paste raw PageSpeed Insights JSON into ChatGPT?
Raw PSI JSON is typically 500KB to 2MB. Most of that is noise for AI agents: base64-encoded screenshots and filmstrips (300–500KB alone), hundreds of passing audits you do not need to fix, treemap visualization data, and internal Lighthouse config metadata. It often exceeds AI context limits or wastes tokens on irrelevant data. PageSpeed Exporter's buildAIReport() function strips all of that and delivers a focused AIReport under 50KB — scores, Core Web Vitals, CrUX field data, stack-specific hints, and a prioritized list of failing audits with estimated savings. Same Lighthouse engine, fraction of the size, every actionable finding preserved.
What is PageSpeed Exporter?
PageSpeed Exporter runs a live Google PageSpeed Insights (Lighthouse) audit on any public URL and exports a stripped-down AIReport JSON — not the raw 2MB PSI dump. It removes screenshots, filmstrips, and passing audits while keeping every actionable finding: scores, Core Web Vitals, CrUX field data, stack-specific hints, and prioritized issues. The result fits in AI context windows and is structured for ChatGPT, Claude, Cursor, and other coding agents to produce precise, code-level fixes.
How do I export PageSpeed Insights results as JSON?
PageSpeed Exporter does this automatically. Enter any URL on the homepage, choose your analysis strategy (Mobile, Desktop, or Both), and run the audit. The results page provides a "Download AIReport (JSON)" button that exports the stripped Lighthouse data — under 50KB of prioritized failing audits, metrics, and CrUX field data — ready to paste into any AI agent.
How do I get Lighthouse results in JSON format?
There are three ways to get Lighthouse results as JSON: (1) PageSpeed Exporter — the easiest option, strips raw PSI data into an AI-ready AIReport under 50KB; (2) the Lighthouse CLI with the --output=json flag (returns the full unprocessed dump); or (3) the Google PageSpeed Insights API directly (also returns the full raw response). PageSpeed Exporter is the only method that also removes noise and includes AI prompt templates.
How do I fix Core Web Vitals using AI?
The most effective workflow is: (1) Run a PageSpeed Exporter audit on your URL to get the full Lighthouse JSON report. (2) Download the JSON file. (3) Open ChatGPT, Claude, Cursor, or your preferred AI agent. (4) Attach or paste the JSON along with a prompt like "Analyze this Lighthouse report and give me the top 5 fixes for LCP with exact code changes." The AI agent will identify the specific issues, explain why they hurt performance, and provide concrete code changes — all because it has the complete structured data rather than a screenshot of a dashboard.
What is the Lighthouse JSON schema?
The Lighthouse JSON report (technically called a Lighthouse Result, or LHR) is a large structured object containing: meta (URL, fetch time, environment), categories (performance, accessibility, best-practices, SEO scores scaled 0–100), audits (150+ individual checks, each with a score, title, description, and details), and loadingExperience (real-user CrUX field data including LCP, FCP, CLS, and INP). PageSpeed Exporter distils this raw report — which can be 500KB to 2MB — down to a focused AIReport object under 50KB, stripping screenshots and binary data while preserving every actionable audit.
How do I feed Lighthouse data to ChatGPT or Claude?
After running an audit in PageSpeed Exporter, click "Copy Prompt" to get the AI report JSON bundled with a ready-to-use prompt. Paste this directly into ChatGPT, Claude, or any AI chat interface. For Cursor or Copilot, download the JSON file and attach it in the chat panel. PageSpeed Exporter includes specialized prompt templates — Full Analysis, Plain English (non-technical), Quick Wins, Code Diffs, and Performance Score — each tuned for a different use case.
What is the difference between PageSpeed Exporter and GTmetrix?
GTmetrix, like most performance tools, outputs a visual dashboard designed for humans. PageSpeed Exporter outputs structured JSON designed for AI agents. GTmetrix is best when you want charts and a visual report to share with a client. PageSpeed Exporter is best when you want to drop the data into ChatGPT, Claude, or Cursor and get exact code fixes. PageSpeed Exporter also runs both Mobile and Desktop audits simultaneously (on paid plans), which GTmetrix charges separately for.
What is the difference between PageSpeed Insights and PageSpeed Exporter?
Google PageSpeed Insights (pagespeed.web.dev) runs the same underlying Lighthouse engine but presents results as a visual web UI with no export button. The PSI API returns 500KB–2MB of raw JSON — mostly screenshots and passing audits. PageSpeed Exporter wraps the same API and strips that down to a focused AIReport under 50KB, with AI prompt templates and mobile + desktop in a single run.
Do I need to create an account to use PageSpeed Exporter?
No account is required to get started. Anonymous visitors can run 2 free preview audits per 30 days with no sign-up. Creating a free account gives you 5 reports per month with browser-local history. Paid plans start at $9/month (Starter) for 50 reports with mobile and desktop analysis and all AI prompt templates.
What are Core Web Vitals and why do they matter?
Core Web Vitals are a set of real-world performance metrics defined by Google: Largest Contentful Paint (LCP) measures loading speed, Interaction to Next Paint (INP) measures responsiveness, and Cumulative Layout Shift (CLS) measures visual stability. Google uses Core Web Vitals as a search ranking factor. Poor scores directly impact both user experience and organic search traffic. PageSpeed Exporter reports all Core Web Vitals alongside lab metrics (FCP, TBT, Speed Index, TTI) and CrUX real-user field data.
Can I use PageSpeed Exporter for client reporting?
Yes. The Pro plan ($29/month) supports batch ZIP export, which lets you run audits across multiple client sites and bundle the JSON reports into a single download for deliverables. Before/after comparison is available on Starter and Pro plans, making it easy to demonstrate performance improvements to clients.
How does PageSpeed Exporter handle my data?
Audit results for anonymous users are stored only in your browser's localStorage — they never leave your device. For signed-in users on Starter or Pro plans, the JSON report is saved to a secure cloud database (Supabase) so you can access it across devices. The Google PageSpeed Insights API is called server-side — your URL is sent to Google's infrastructure to run the Lighthouse audit, the same as visiting pagespeed.web.dev directly.
Can I use my own Google API key?
Yes. PageSpeed Exporter accepts an optional custom Google API key in the analysis form. This is useful for power users who want to use their own Google Cloud quota. If you provide your own key, it is passed directly to the Google PageSpeed Insights API and is never stored on our servers.
Ready to try it?
Run your first audit and get a stripped AIReport JSON in under 30 seconds — under 50KB, every actionable finding, no account required.
Analyze a URL for freePerformance glossary
Learn what each metric means and how to improve it:
Still have questions? Contact us