Comparison · checked 2026-11-14

Free AI tools to fix PageSpeed Insights issues

Written by the maker of Lighthouse-MD, one of the tools below. Facts about the other tools come from their own pages on that date.

Quick answer: Five free tools use AI (or hand data to your AI) to fix PageSpeed Insights issues. DeployHQ AI PageSpeed and Peplio write fix suggestions you read in the browser. The PageSpeed Insights MCP server lets your AI client call PageSpeed itself. Lighthouse-MD turns the full report into a CLAUDE.md fix plan your coding agent applies in your repo. PageSpeed Insights gives the official numbers, without AI.

Which free AI tools fix PageSpeed Insights issues?

ToolWhat you getBest forCost and signupLimits
Lighthouse-MDA CLAUDE.md fix plan: every failing audit in all five Lighthouse categories, ranked offenders (URLs, selectors, HTML), the passing audits not to break, throttling profile, third-party and main-thread breakdown. Chrome extension and an optional weekly re-check email.Handing the fix to an AI coding agent (Claude Code, Cursor, Codex) that edits your repoFree. Scores need no signup; the CLAUDE.md asks for an email once.Public URLs only (it runs through PageSpeed Insights)
DeployHQ AI PageSpeedAI-written recommendations with steps, code or config examples, predicted impact and priority. Detects your framework. A “Prompt for AI Agents” button copies a prompt to paste into an assistant.Reading fixes in the browser and applying them yourselfFree, no signup, per their pagePublic pages only. Results are not stored.
Peplio Website Speed Analyzer6 to 8 AI recommendations with priority, difficulty and time saved. Plain-text report export.A quick prioritized list, often naming WordPress plugins and hostsFree, no email3 analyses per hour per IP. Public pages only.
PageSpeed Insights MCPAn open-source MCP server: your AI client runs PageSpeed and Chrome UX Report checks, compares pages and keeps baselines. Markdown or JSON output.Letting an agent fetch performance data on demand inside a sessionFree, Apache-2.0. Needs a Google API key and Node 20.Your own API key quota
PageSpeed InsightsGoogle’s official lab and field (real-user) data with Lighthouse audits. No AI.The reference numbers every tool above readsFree, no signupPublic pages only

How are these AI PageSpeed tools different?

They split on one question: does an AI rewrite the report, or does your agent get the report itself?

None of them change how Google measures you. They all read the same PageSpeed Insights data.

Which one should I use?

These combine well. PageSpeed Insights for the truth, one of the others for the fix.

Turn your PageSpeed report into a CLAUDE.md fix plan →

Do AI PageSpeed tools improve my score by themselves?

No. Every tool here reads PageSpeed Insights; none of them change your site until you or your agent apply a fix. Also expect the Performance score to move about 5 points between runs with no code change, because lab tests vary. Judge a fix on the metric it targets (LCP, TBT, CLS), not one score. The audit explainers cover the fixes one audit at a time.

FAQ

Is there a free AI tool to fix PageSpeed Insights issues?

Yes. DeployHQ AI PageSpeed and Peplio give free AI-written fix suggestions. Lighthouse-MD is free and turns the report into a CLAUDE.md fix plan for an AI coding agent. The PageSpeed Insights MCP server is free and open source but needs your own Google API key.

Can Claude Code fix PageSpeed Insights issues?

Yes, if it has the audit data. Claude Code cannot see your PageSpeed report on its own. Give it the report as a CLAUDE.md brief (Lighthouse-MD), or connect a PageSpeed MCP server so it can fetch the data, then ask it to fix the failing audits and re-run the test.

Which AI PageSpeed tool works without a Google API key?

Lighthouse-MD, DeployHQ AI PageSpeed, Peplio and PageSpeed Insights itself all work in the browser with no key. Only the MCP server needs one, because it calls the PageSpeed API from your machine.

How we checked

Each tool’s features, price, signup and limits come from its own website or repository on 2026-11-14. Vendor claims were not independently tested. If something here is wrong or out of date, tell the maker on LinkedIn and it will be corrected.