Website Speed Test
Type a web address, pick mobile or desktop, and press the button. In about half a minute you get a speed score from 0 to 100, five timing measures and the changes that would help most.
The test is run by Google’s PageSpeed Insights, using the same Lighthouse tool that web developers use. You also get scores for accessibility, best practices and SEO.
Please note: Scores come from Google PageSpeed Insights (Lighthouse) and describe one test from Google’s servers. They are a guide, not a guarantee of how your visitors experience the site.
How it works
When you press the button, our server asks Google to load your page in a test browser, on a simulated phone or desktop. Google measures how the page behaves and sends back the results. We trim them down to the useful parts and show them here.
The speed score is a mix of five measures. First Contentful Paint is when something first appears. Largest Contentful Paint is when the main content is there. Total Blocking Time is how long the page freezes and ignores taps and clicks. Cumulative Layout Shift is how much the page jumps around while loading. Speed Index is how quickly the page fills in. Each is rated Good, Needs work or Poor using the ranges Google publishes.
A score of 90 or above is good, 50 to 89 needs work and below 50 is poor. Mobile scores are almost always lower than desktop, because the test simulates a slower phone on a slower network.
If the site gets enough visitors, Google also has “real user data” for it, collected from Chrome users over the last 28 days. When that exists it is shown too, and it matters more than the lab test, because it comes from real people.
Results come from Google’s servers, in one place, at one moment. Your own visitors in other places and on other devices will see different numbers. Run the test a few times and treat small changes as noise. We keep a result for 10 minutes, so testing the same page again right away shows the same answer.
Worked example: Reading a result
Say a page scores 87 on mobile. That is “Needs work”, close to good. If the largest content takes 2.6 seconds and the limit for “Good” is 2.5 seconds, that one measure is just over the line, and it is where to look first.
The “biggest fixes” list shows what Google thinks would save the most time, such as compressing images or removing unused JavaScript. Fixing the top one or two usually gives most of the gain.
Frequently asked questions
What is a good speed score?
90 to 100 is good. 50 to 89 needs work. Under 50 is poor. Most real sites score lower on mobile than desktop.
Why is my mobile score so much lower?
The mobile test simulates a mid-range phone on a slow connection, so heavy pages take much longer. It is on purpose, because many visitors use phones.
Why does my score change between tests?
Servers, networks and the test itself all vary a little. A few points either way is normal. Look at the trend over several runs.
Does page speed affect Google rankings?
Speed is one of many signals. A very slow page can hurt both rankings and visitors, who leave. A fast page is rarely the thing that holds a site back on its own.
What do you send to Google?
The web address you type, and nothing else. We do not store it. See the privacy page.
Why did my test fail?
The page may be offline, block automated visitors, need a login or take too long to load. Check the address and try again. Sites that block Google’s test browser cannot be tested.
Related tools
- Ping TestRun a quick ping test in your browser. See your latency, jitter and lost requests, with a plain verdict on gaming and video calls. Free, no download.
- What Is My IP AddressSee your public IP address in one click, and whether it is IPv4 or IPv6. Optional location and network details. No sign-up.
- IP LookupLook up any IPv4 or IPv6 address to see its country, region, city, time zone and network provider. Checks the address format first.
Sources
Content last reviewed 2026-10-13.