What does the website speed test do?
This tool runs your page through Google PageSpeed Insights, the same engine Google offers to developers, and presents the results simply. You get four scores out of 100 (Performance, Accessibility, Best Practices and SEO) for the device you choose.
Where Google has enough visits from real Chrome users, you'll also see field data for the three Core Web Vitals: Largest Contentful Paint (LCP), how fast the main content appears; Interaction to Next Paint (INP), how quickly the page responds to taps and clicks; and Cumulative Layout Shift (CLS), how much the layout jumps while loading. This real-user data is what Google uses in its page experience signals.
Below that are lab metrics from a simulated test, plus the biggest opportunities ranked by how much time they could save, such as unused JavaScript, oversized images or render-blocking stylesheets.
Using the Website Speed Test for your business
A slow score usually comes from the theme, images or third-party scripts, and it affects both rankings and conversion rates. Our technical SEO service fixes Core Web Vitals on real templates, not just the homepage. If you run ads, faster landing pages also improve Quality Score, which our Google Ads management team tracks closely.
How to use the Website Speed Test
- Enter a page URL. Test your home page first, then your most important landing pages.
- Choose mobile or desktop. Start with mobile: most visitors use phones and Google indexes the mobile version.
- Click Test speed. The test takes 20–60 seconds while Google loads and measures the page.
- Read the scores and Core Web Vitals. Green is good, amber needs improvement, red is poor.
- Work through the top fixes. Start with the opportunities that save the most time, then test again.
Why test your website speed
Real-user data
See Core Web Vitals from actual Chrome visitors, not just a lab test.
Prioritised fixes
Opportunities are ranked by potential time saved.
Mobile and desktop
Test both, because results often differ a lot.
Plain-English results
Clear statuses instead of a wall of technical audits.
What counts as a good score?
Google's thresholds for a good experience are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of visits. Pages that meet all three pass the Core Web Vitals assessment.
The Performance score out of 100 is a lab summary and can vary a few points between runs because of network conditions. Don't chase a perfect 100; focus on passing Core Web Vitals and on the fixes that save the most time.
The usual culprits on slow sites are large images (fix them with our image compressor and WebP converter), too many plugins and third-party scripts, slow hosting with a high time to first byte, and fonts that block rendering. If several pages fail, a technical review of templates and hosting usually fixes them all at once.
Test the same pages on a regular schedule, for example after every major plugin update or design change, so you catch regressions early. Keep a simple log of the date, the Performance score and the three Core Web Vitals for each key page. Trends over a few weeks tell you far more than any single test.
Frequently asked questions
Is this the same as Google PageSpeed Insights?
Yes. The data comes from Google's PageSpeed Insights API; we present it in a simpler format.
Why is my mobile score lower than desktop?
Mobile tests simulate a slower phone and network, so heavy pages suffer more. Most visitors use mobile, so prioritise it.
Why does my score change between tests?
Lab tests vary slightly with network and server load. Look at trends and Core Web Vitals rather than single scores.
Why is there no real-user data for my page?
Google only shows field data when the page has enough Chrome visits. New or low-traffic pages show lab data only.
Does page speed affect Google rankings?
Yes, page experience including Core Web Vitals is a ranking signal, though relevance and content quality matter more.