A free page speed checker that runs Google's own test on a phone and shows the scores, real visits and what to fix first.
Type any page to run Google's own speed test on a phone: the scores, the page loading frame by frame, and real Chrome visits.
Page speed is how fast a page loads and responds, the way a visitor actually feels it.
This free page speed checker runs Google's own test on any page, on a simulated phone, and adds real visit data from Chrome when the page has enough of it.
You get the scores, the timings, the page loading frame by frame, and every failing audit with what it costs, plus the full SEO report of the same page underneath.
I built it because I wanted Google's test and the rest of the page's checks in one place, instead of jumping between tools.
So here's what the numbers mean, how much speed really matters for Google, and what I'd fix first.
Key takeaways
What is a page speed checker?
A page speed checker is a tool that loads a page the way a visitor would and tells you what slowed it down.
This one runs Google's own Lighthouse test through PageSpeed Insights, so the numbers match what Google's tools show.
The three Core Web Vitals
Google sums up a page's experience in three numbers, and web.dev sets the target for each:
- What it measures
- How long until the biggest thing on screen shows
- Good
- 2.5 seconds or less
- What it measures
- How fast the page responds to a tap or click
- Good
- 200 ms or less
- What it measures
- How much the page jumps around while it loads
- Good
- 0.1 or less
web.dev measures each one at the 75th percentile of page loads, so three out of four visits should get a good result.
How much speed matters for Google
Google says plainly that Core Web Vitals are used by its ranking systems.
But it also says it always shows the most relevant content, even when the page experience is sub-par... and that experience counts for more when several pages are similar in relevance.
So for me, speed is a tiebreaker you want on your side, and a reason people stay, more than a way to jump past better content.
Lab test and real visits
The report shows two kinds of numbers, and it helps to know which is which:
- The lab test – Google loads the page once on a simulated phone and times it. It's the same every time, which makes it the best way to find and fix problems.
- Real Chrome visits – what real visitors got over the last 28 days, from Chrome's own data. It shows the page's own visits when it has enough, and the site's when it doesn't.
When the two disagree, the real visits are what your visitors live with... and the lab test is how you find out why.
What the page speed checker shows
- What it shows
- Performance, accessibility, best practices and SEO
- What to do with it
- Start with the lowest
- What it shows
- First paint, largest paint, blocking time, layout shift and more
- What to do with it
- Compare them with the targets above
- What it shows
- 28 days of real visitors, when there are enough
- What to do with it
- The numbers Google judges you on
- What it shows
- The page loading frame by frame
- What to do with it
- See what appears first and what holds it up
- What it shows
- Every check that failed, with what it costs
- What to do with it
- Fix the biggest savings first
- What it shows
- A score, every check and what to fix first
- What to do with it
- The rest of the page, in the same run
How to check your page speed
A real example: my guide to starting a blog
I ran my own how to start a blog guide, a page of over 14,000 words, through the checker twice on the same day.
- First run
- 79
- Second run
- 68
- First run
- 91
- Second run
- 91
- First run
- 100
- Second run
- 100
- First run
- 92
- Second run
- 92
- First run
- 4.2 seconds
- Second run
- 5.5 seconds
- First run
- 265 ms
- Second run
- 368 ms
- First run
- 0.017
- Second run
- 0.017
The layout barely moves, which is great, but the largest paint is well over Google's 2.5 seconds in both runs... so on a phone, that's the one number I'd work on first.
And look how much performance moved between two runs of the same page. That's why I never judge a page by one lab test.
Chrome didn't have enough real visits for field data yet, even for the site overall... so for now, the lab test is all there is.
What slows most pages down
These are the causes I see over and over, roughly in order:
- Big images – a hero image in full size is the usual reason the largest paint is slow.
- Fonts – several font files, loaded before the text can show.
- Scripts – chat widgets, trackers and tag managers that block the page while they load.
- Layout shifts – images and ads without a set size, pushing text down as they arrive.
- A slow server – every step waits on the first byte.
How I'd fix a slow page
Mistakes to avoid
- Chasing a score of 100 instead of the three vitals
- Testing only on desktop, when most visits are on phones
- Judging a page by one lab run when real visits say otherwise
- Adding a new plugin for every fix, which adds more scripts
- Lazy loading the hero image, which delays the largest paint
Who is the page speed checker for?
It's for anyone whose visitors wait for a page to load:
- How to start a blog – bloggers checking a new theme before they launch
- How to create an online course – course creators testing a sales page
- How to host a virtual summit – summit hosts testing a registration page before traffic hits
- Internet speed test – anyone who wants to check their own connection first
- SEO checker – site owners who want every check in one run
And if you change themes or add a big plugin, run it again, because that's usually when speed drops.
After you check your page speed
| Tool | Use it when |
|---|---|
| SEO checker | You want every other check on the page |
| Broken link checker | Slow pages link to others that no longer load |
| Heading checker | You want the page easier to skim once it's fast |
| Internet speed test | You want to rule out your own connection |
Check the rest of the page
Page Speed Checker FAQs
Questions about page speed? Here's what to know.
It's a tool that loads a page like a visitor would and times every step.
This one runs Google's own Lighthouse test.
They're Google's three measures of page experience: loading, responsiveness and visual stability.
They're called LCP, INP and CLS.
2.5 seconds or less, for at least three out of four visits.
It's the time until the biggest thing on screen shows.
200 milliseconds or less.
It's how fast the page responds to a tap or click.
0.1 or less.
It measures how much the page jumps around while it loads.
Yes, Google says its ranking systems use Core Web Vitals.
It still shows the most relevant page first, even when another is faster.
The lab test runs on a simulated phone, and the network and server vary each run.
My own guide scored 79 and then 68 on the same day, so look at a few runs.
Chrome's data only appears when the page, or its site, has enough real visits.
Newer or quieter sites show the lab test only.
Most visits are on phones, and phones are slower.
A page that's fast on a phone is fast everywhere.
Big images and scripts, in most cases.
The failing audits show which one costs your page the most.
About 40 seconds, while Google loads the page and times it.
The rest of the report shows first.
Yes, it's free, with no sign-up.
I did. I'm Navid Moazzez, and I made the page speed checker as one of my free tools on navid.me.
You can read more about me.
Navid.me is reader-supported. When you buy through links on this site, I may earn an affiliate commission. Learn more.
More free tools
Related MCP servers & CLIs
Free AI newsletterThe most actionable AI newsletter for founders
Every week, get proven AI strategies, curated tools, and step-by-step systems to grow your audience, create better content, and build a profitable creator business.
No fluff, no filler, no BS. Just five minutes each week that might level up your online business and life.
P.S. Sign up now to get free access to my ultimate AI tools guide for creators.






