Turn Your PageSpeed Report into a Plain-English Fix List for Your Website

Get each failing Core Web Vitals metric explained as what visitors experience, plus fixes sorted by impact and effort and marked DIY or developer.

You getQuick verdict, table and table

Prompt

Prompt
You are a web performance consultant who explains technical reports to small business owners with no coding background.

I will paste my PageSpeed Insights or Core Web Vitals report right after this message. Turn it into a fix list I can act on. If you cannot tell which website builder I use, ask me once before answering.

Rules:
1. For each failing or needs-improvement metric (LCP, INP, CLS, FCP, TBT, Speed Index), give my score and one sentence on what a visitor actually experiences, e.g. "the main photo appears 5 seconds after the page opens."
2. Only list fixes tied to something in the report. Do not invent numbers or issues.
3. Rate each fix for effort and impact (Low/Medium/High) and sort so high-impact, low-effort fixes come first.
4. Mark each fix "DIY in builder" or "Needs developer" and say why in a few words.
5. Explain any technical term in one short line.

Output format:
- Quick verdict: 2-3 sentences, mobile vs desktop.
- Table: Metric | My score | Target | What visitors experience
- Table: # | Fix | Metric it helps | Effort | Impact | DIY or developer | How to start
- Do these 3 first: numbered list.

End with one line on what the report cannot show (e.g. real-user data if only lab data was pasted) and any assumptions you made.

Example output

At a glanceBakery homepage metrics: current score vs targetMobile PageSpeed score 38, desktop 81
ItemMy scoreTarget
LCP (Largest Contentful Paint)5.8 sunder 2.5 s
CLS (Cumulative Layout Shift)0.24under 0.1
TBT (Total Blocking Time)890 msunder 200 ms
FCP (First Contentful Paint)2.9 sunder 1.8 s

Example for: a neighborhood bakery's Squarespace homepage, mobile score 38, desktop score 81.

Quick verdict

Your desktop site is in decent shape, but mobile is slow, and most local customers will find you on a phone. The biggest problems are a heavy hero image and content that jumps around while loading. Most of the fixes are things you can do yourself in Squarespace.

What visitors experience

MetricMy scoreTargetWhat visitors experience
LCP (Largest Contentful Paint)5.8 sunder 2.5 sThe big croissant photo takes almost 6 seconds to appear, so the page looks empty at first.
CLS (Cumulative Layout Shift)0.24under 0.1The menu button moves down as the banner loads, so people tap the wrong thing.
TBT (Total Blocking Time)890 msunder 200 msThe page looks ready but ignores taps for nearly a second.
FCP (First Contentful Paint)2.9 sunder 1.8 sVisitors stare at a blank white screen for about 3 seconds.

Fix list

#FixMetric it helpsEffortImpactDIY or developerHow to start
1Shrink the hero image (report flags 2.4 MB)LCP, FCPLowHighDIY in builder: just re-upload a smaller fileResize to 1600 px wide, compress to under 300 KB, re-upload
2Remove the unused Instagram feed blockTBTLowHighDIY: delete the blockLink to Instagram with a button instead
3Give the announcement banner a fixed spotCLSLowMediumDIY: change banner settingsTurn off the animated slide-in effect
4Drop one of the three custom fontsFCPLowMediumDIY: Site Styles panelUse one heading font and one body font
5Remove the third-party chat widget scriptTBTMediumMediumNeeds developer if added via code injectionCheck Settings > Advanced > Code Injection
6Defer the custom JavaScript for the order formTBTHighMediumNeeds developer: requires editing codeAsk them to load it only on the Order page

Jargon: "Defer" means telling the browser to load a script after the page is visible.

Do these 3 first

  1. Compress and re-upload the hero image.
  2. Delete the Instagram feed block.
  3. Turn off the banner slide-in animation.

Note: This report shows lab data only, not real-visitor data, so real phone speeds may differ. I assumed Squarespace based on the script names in the report.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Translating each metric into what a visitor sees makes abstract scores like CLS 0.24 urgent and understandable.
  • Sorting by impact versus effort puts quick wins first so owners fix what matters before hiring help.
  • The DIY-or-developer label stops owners paying a developer for tasks they can do in their builder settings.

Use after running your homepage or a key page through PageSpeed Insights. Copy the full report text, including the diagnostics section, and paste it after the prompt in ChatGPT, Claude or Gemini.

Common edits

  • Name your builder up front (e.g. Wix or Shopify) to get exact menu paths.
  • Ask for a short email you can forward to a developer covering only the developer fixes.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in SEO