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
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
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.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit template image tags for layout shifts
Review image tags in template code for missing width, height, and incorrect lazy-loading rules. Use it to fix Cumulative Layout Shift and LCP issues.
Audit site crawl data to rescue orphaned and buried pages
Turn crawl reports into an actionable internal linking strategy to restore crawl paths for high-value pages with zero internal links.
Audit XML Sitemap Structure for Large Websites
Get a structured audit of your XML sitemap hierarchy that identifies potential indexing bottlenecks based on search engine crawl limits.
Diagnose Why Your Local Business Is Not Showing in the Google Map Pack
Get a ranked diagnosis of why your business is missing from Google's top 3 map results, sorted by relevance, distance and prominence, plus a 30-day DIY fix order.
Plan a Month of Google Business Profile Posts for Your Local Business
You get a four-week Google Business Profile post calendar that mixes offer, update and event posts, each under 300 characters with one matching button.
Find Keyword Cannibalization in Your URL and Ranking Data with Fix Actions
Get your competing pages grouped by search intent, with a primary URL and a merge, redirect, differentiate or keep action for each, backed by your ranking data.