Skip to content
SiteFaults

Free page speed checker

A page speed checker that runs Google's own Lighthouse analysis and gives you the performance score plus the load timings behind it — First Contentful Paint, LCP, blocking time and more — for both mobile and desktop, so you can see exactly which phase is slow.

Enter the exact page you want measured. The score and timings come from Google's own Lighthouse run.

Read the timings, not just the score

The single performance number is a useful headline and a poor diagnosis. Two pages can both score 60 for completely different reasons — one because its largest image paints late, the other because a pile of JavaScript blocks the main thread. The timings underneath are where the fix lives. A slow Largest Contentful Paint points at a heavy hero image or a slow server response; a high Total Blocking Time points at script execution; a non-zero Cumulative Layout Shift means content is jumping as the page loads. The score tells you there is a problem; the timings tell you where it is.

Test mobile first

The mobile profile throttles the CPU and the network to mimic a real phone, which is why its score sits well below desktop on most sites. That is not the tool being harsh — it is the experience most of your visitors actually get. If you optimize one profile, make it the mobile one, and treat the desktop score as the easier target you will clear along the way.

Lab data versus field data

This is a lab test: one controlled load under fixed conditions, ideal for iterating on a fix because it is repeatable. What it cannot tell you is whether real visitors, on their real devices and connections, feel the same thing. That is field data, and it is what Google actually ranks on. Once you have made a page faster here, confirm it with the Core Web Vitals checker, which reads Google’s real-user measurements for the three metrics that count toward ranking.

Where this fits

Speed is one input among many, and the fastest page on the internet still will not rank if it is blocked from indexing or has nothing to say. The free website checker runs speed alongside technical SEO, metadata, accessibility and AI-search visibility and scores the whole thing out of 100, and what counts as a good score puts the number in context. If a slow response time is the culprit, the HTTP header checker shows whether caching and compression are configured.

Page speed questions

What does this page speed checker measure?
It runs Google's Lighthouse analysis on the URL you enter, for both a mobile and a desktop device profile, and returns the overall performance score out of 100 plus the individual load-phase timings behind it: First Contentful Paint, Speed Index, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift and Time to Interactive. Each timing is scored so you can see which phase is dragging the number down.
What is a good page speed score?
On Lighthouse, 90 to 100 is good, 50 to 89 is a mid-range that needs work, and below 50 is poor. Mobile scores are almost always lower than desktop because the test uses a throttled connection and a slower CPU to mimic a real phone — so judge the mobile number against mobile expectations, not against your desktop result.
Why is my mobile score so much lower than desktop?
The mobile test deliberately simulates a mid-tier phone on a slow 4G connection: reduced CPU speed and constrained bandwidth. Desktop assumes a fast wired connection and a capable processor. A large gap usually points at heavy JavaScript that a phone's slower CPU struggles to execute, or large images being downloaded over the throttled connection. Since most traffic is mobile, the mobile score is the one to optimize for.
Is this the same as Core Web Vitals?
They overlap but answer different questions. This tool is a lab test: one controlled Lighthouse run that gives you the overall performance score and every load-phase timing, which is what you want while diagnosing and fixing a slow page. Core Web Vitals, by contrast, is field data from real Chrome users over the past 28 days for the three metrics Google ranks on. Use the page speed checker to fix, and the Core Web Vitals checker to confirm real users feel the improvement.
Does page speed affect SEO?
Yes. Speed feeds Core Web Vitals, which is a confirmed Google ranking signal, and it affects rankings indirectly through bounce rate and engagement. The effect is real but not dominant — a fast page with thin content still will not rank. Treat speed as a multiplier on good content rather than a substitute for it.
Why does the test take longer than other tools?
Because it is doing far more work: Google is loading the entire page in a real headless browser, executing its JavaScript, and measuring each phase of the render — for two device profiles. That is a genuine page load rather than a quick HTML fetch, so it can take up to a minute. The depth is the point; a result in under a second would only be reading the markup, not measuring the experience.
The score changes between runs — why?
Lab tests vary a little run to run because network conditions, ad and third-party script response times, and server load all shift between measurements. A swing of a few points is normal. If you are testing a fix, run it two or three times and compare the range rather than reading a single number as exact.
Why is my website loading so slowly?
Slow loading usually traces to a few repeat offenders: oversized images, too much JavaScript, a slow server response, and render-blocking scripts and stylesheets. Run the test above to see which of these dominates on your page, since fixing the largest single cause typically moves the needle more than many small tweaks.
How do I speed up a slow WordPress website?
The highest-impact steps on WordPress are adding a caching plugin, compressing and correctly sizing images, choosing a fast host, and removing plugins that inject scripts on every page. Measure after each change so you keep what helps and can tell which plugin was the real drag.
What is a good page load time?
Aim to have the main content usable within about two and a half seconds on a typical mobile connection, which aligns with Google's 'good' threshold for Largest Contentful Paint. There is no single official number for total load, so focus on when the page becomes useful rather than when the last byte arrives.
Does image size affect page speed?
Image weight is one of the biggest causes of slow pages, because an uncompressed or oversized image can be many times larger than all the text and code combined. Serving images in a modern format like WebP, at the dimensions they actually display, is usually the fastest single improvement available.
What is the difference between page speed and site speed?
Page speed is how fast one specific URL loads, while site speed is an aggregate impression across many pages. Optimisation happens at the page level because each page has its own images, scripts and content, so this tool measures a single URL at a time.