Fix report
Performance Fix Report
We load your three key pages (on a store: home, collection and product) as a mid-range phone on slow 4G, add Google’s real-user data when your site has enough traffic, and show what slows each page down with the fixes in order.
- Mobile lab test (LCP, CLS, TBT)
- Google real-user data when available
- Heaviest images and scripts
What we check
Largest Contentful Paint
How long the main content takes to appear on a throttled phone, against the 2.5 second threshold.
Layout shift
Whether content jumps around while loading, against the 0.1 threshold.
Total Blocking Time
How long scripts keep the page from responding, the lab stand-in for Interaction to Next Paint.
Real-user data
LCP, INP and CLS at the 75th percentile from Google’s Chrome UX Report, when your site has enough traffic to appear in it.
Heavy and oversized images
Images over 150 KB, or much larger than the size they are shown at, and a lazy-loaded main image.
Page weight and requests
Total download size, the number of requests and the share that comes from third parties.
Render-blocking files
Scripts and stylesheets that hold up the first paint.
What you get
- Measured numbers for each page, with thresholds
- The heaviest files on each page, by size
- Fixes in order of impact, written for your platform
- A ready-made AI prompt for every finding
- A PDF to share with your developer
How the report is made
- 1
Each page is loaded in a fresh browser emulating a mid-range phone, with slow 4G (150 ms latency, 1.6 Mbps) and a 4× slower CPU.
- 2
Google’s Chrome UX Report is queried for your origin’s real-user data.
- 3
The causes are ranked by how much they cost and written up with fixes.
Findings from the sample report
Real output for Harbor & Pine, a fictional store we built with common problems.
- Problem
The main content appears slowly on phones
Largest Contentful Paint reached {time} on {path} in our phone test (good is under 2.5 s).{"time":"{s} s{\"s\":{\"$num\":8.3,\"digits\":1}}","path":"/products/trail-daypack"}
Fix: Start with the largest image or banner at the top of the page (see the findings below).
- Problem
The main image is lazy-loaded
On {n} page(s) the largest image at the top has {attribute}, which delays it.{"n":1,"attribute":"loading=\"lazy\""}
Fix: Load the first, largest image eagerly and give it high fetch priority; keep lazy loading for images further down.
- Problem
Images larger than they need to be
{n} image(s) are heavy (over 150 KB) or much wider than they are shown.{"n":2}
Fix: Upload product and banner images at sensible sizes (around 2000 px wide is plenty) instead of camera originals.
What it doesn’t cover
- Desktop speed
- Server and hosting configuration
- Guaranteed scores: lab results vary between runs
Questions about this report
Why test on a slow phone?
Many visits happen on phones, and Google’s Core Web Vitals are measured separately for mobile. A throttled phone shows problems a fast laptop hides.
What if my site has no Chrome UX Report data?
Smaller sites often don’t have enough traffic to appear in it. The report then relies on the lab test and says so.
Is INP measured?
INP needs real interactions, so it comes from Google’s real-user data when available. The lab test reports Total Blocking Time, which tracks the same problem.
Will my PageSpeed score match?
Not exactly. Lab results vary between runs and tools use slightly different settings, but the causes they point to are the same.
Other reports
- Accessibility Fix ReportList price $249, launch price $174
- EAA Readiness ReportList price $199, launch price $139
- SEO Fix ReportList price $99, launch price $69
- Conversion ReportList price $149, launch price $104
- Website Security ReportList price $99, launch price $69
- Email Deliverability ReportList price $49, launch price $34
Scan your website today
Find it. Fix it. Verify it.
Free scan. No credit card required.