For site owners and developers

Turn a PageSpeed report into a fix list

The Page Speed Fix Planner reads your PageSpeed Insights or Lighthouse report and turns it into a prioritised plan: which Core Web Vitals pass or fail, what is causing each problem, the fixes ranked by impact and effort, and the code or settings for your platform, explained in plain English.

Free, no sign-up
Results in about 30 seconds
10 runs a day
Input not stored

mohitgoyal.in/tools/page-speed-fix-plannerFree · 10 runs a day

Page Speed Fix Planner

A ranked fix list from your PageSpeed report

Result· Ready

Your result will appear here

Fill in the form, or press Try an example to see what you get:

Which Core Web Vitals pass or fail
The cause behind each slow metric
Fixes ranked by impact and effort
Code or plugin settings for your platform
A quick-wins checklist to start with

How it works

How to use the Page Speed Fix Planner

Run PageSpeed Insights
Test your page at pagespeed.web.dev and copy the report text.
Paste it with your platform
WordPress, Shopify, Next.js and so on. The fixes are written for your setup.
Fix in order
Start at the top: the fixes are ranked by how much speed they win for the effort.

What you get

Inside every result

Which Core Web Vitals pass or fail
The cause behind each slow metric
Fixes ranked by impact and effort
Code or plugin settings for your platform
A quick-wins checklist to start with

Who it's for

Built for

Site owners with a failing Core Web Vitals report
Marketers whose ads and SEO suffer from a slow site
Developers who want a prioritised plan
Agencies explaining speed work to clients

What Core Web Vitals measure

Largest Contentful Paint (LCP) is how fast the main content appears; good is 2.5 seconds or less. Interaction to Next Paint (INP) is how quickly the page responds to taps and clicks; good is 200 milliseconds or less. Cumulative Layout Shift (CLS) is how much the layout jumps around; good is 0.1 or less.

Lighthouse can't measure INP in a lab test, so Total Blocking Time (TBT) stands in for it: heavy JavaScript that blocks the main thread usually hurts both.

Why fix order matters

Most slow sites have the same few causes: oversized images, render-blocking CSS and JavaScript, too many third-party scripts and missing image dimensions. Fixing the largest one first, usually the LCP image, often moves the score more than ten small tweaks.

Lab data versus field data

The score at the top of PageSpeed Insights is a lab test on a simulated phone. Google ranks on field data from real Chrome users, shown in the 'Discover what your real users are experiencing' section. Both matter, but the field data is what Google uses.

Guides and services

Questions

Frequently asked

Is page speed a ranking factor?+

Yes. Core Web Vitals are part of Google's page experience signals. They rarely beat relevance, but between similar pages the faster one has the edge, and speed affects conversions either way.

Why is my mobile score lower than desktop?+

PageSpeed Insights tests mobile on a throttled mid-range phone and a slow network, so heavy images and JavaScript cost far more there.

Do I need a developer to apply the fixes?+

Many quick wins, such as image compression, lazy loading and caching plugins, are settings. Removing render-blocking code, replacing a page builder or rewriting scripts usually needs a developer.

What is a good PageSpeed score?+

90 or more is good, 50 to 89 needs improvement and below 50 is poor. Passing Core Web Vitals in the field data matters more than the lab score.

Is this tool free?+

Yes. Every tool on this site is free with no sign-up. Each visitor gets 10 runs of each AI tool per day, which keeps the tools fast and available for everyone. The tools that use no AI have no daily limit.

Is what I paste saved or shared?+

No. Your input is sent to the AI model (Claude by Anthropic) only to generate your result, and it is not stored on this site. Still, do not paste passwords, financial details or anything confidential.

More free tools