We run Google PageSpeed Insights on your page as a phone and as a desktop, then show the five numbers behind the score and what to fix first. No email needed.
Speed on a phone
Main content
First paint
Speed index
Blocked input
Layout shift
What to fix
Take it with you
Rather hand it over?
Relaunch starts with an audit of your live product, then we fix what holds it back.
The numbers come from the PageSpeed Insights API, which runs Lighthouse on Google's servers: once as a mid-range phone on a slowed-down mobile connection, once as a desktop. The score is built from these five.
Number
What it measures
Good on a phone
Good on a desktop
Main content (LCP)
When the largest image or text block appears
Under 2.5 s
Under 1.2 s
First paint (FCP)
When anything first appears
Under 1.8 s
Under 0.9 s
Speed index
How fast the screen fills in
Under 3.4 s
Under 1.3 s
Blocked input (TBT)
How long scripts keep the page from responding
Under 200 ms
Under 150 ms
Layout shift (CLS)
How much the layout jumps while loading
Under 0.1
Under 0.1
"Good" here is where Lighthouse starts scoring a number green. Google's Core Web Vitals use 2.5 s for LCP and 0.1 for CLS on every device.
Why the score moves between runs
Each run loads your page fresh, over a network that is never exactly the same twice, so a score can move by a few points. We run each device once and say so on the result. If a number sits near a line, run it again and read the results as a range.
What to fix first
Slow main content. Find what the largest element waits for: a slow server response, scripts that block rendering, fonts that arrive late or a hero image that is too heavy.
Blocked input. Look for long tasks in the browser's performance panel. Third-party scripts such as chat widgets, analytics and tag managers are common causes; many can load after the first interaction instead of during page load.
Layout shift. Give images and embeds a set width and height, and reserve space for anything that appears later, such as cookie banners and fonts.
Is this the same as PageSpeed Insights?
The speed numbers are. We add the fixes in plain words, a prompt you can hand to a coding agent, and the search, sharing and security checks that PageSpeed Insights does not cover. Field data from real Chrome users, which PageSpeed shows for sites with enough traffic, is not part of this test.