Skip to content

Page speed testOn a phone and a desktop

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.

  • Page speedPageSpeed Insights on a phone and a desktop, with the five numbers behind the score.
  • Meta tagsTitle, description, canonical, viewport and noindex: the tags search reads first.
  • Share imageWhether your og:image is there and loads, so a shared link shows a picture.
  • Security headersHTTPS, the redirect to it, HSTS, CSP and the headers around them.
  • Robots and sitemapWhether robots.txt lets crawlers in and points them to your sitemap.

What the five numbers mean

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.

NumberWhat it measuresGood on a phoneGood on a desktop
Main content (LCP)When the largest image or text block appearsUnder 2.5 sUnder 1.2 s
First paint (FCP)When anything first appearsUnder 1.8 sUnder 0.9 s
Speed indexHow fast the screen fills inUnder 3.4 sUnder 1.3 s
Blocked input (TBT)How long scripts keep the page from respondingUnder 200 msUnder 150 ms
Layout shift (CLS)How much the layout jumps while loadingUnder 0.1Under 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.

More single checks