Free website speed test
Find out how your website performs on a phone, what real visitors experience, and which problems are worth fixing first.
The check runs Google's Lighthouse test on a simulated phone by default, with a desktop option. It explains the speed, accessibility and search basics behind the result. If Google has enough real-visitor data, it also shows Core Web Vitals.
Loading the page on a test phone...
Measured once on a simulated device and connection. Results vary a little between runs.
Reading the results
Scores are a guide, not a goal. What matters is whether visitors can see the page quickly, use it without frustration and find the next step.
When Google has enough Chrome visitors to your page, it reports the last 28 days of real-world experience. Use that history to judge visitor impact and the one-off Lighthouse test to investigate causes. Some pages have too little field data to show it.
Google's guidance is that the largest image or text block should appear within 2.5 seconds on a phone, the page should respond to taps within 200 milliseconds, and the layout should not jump.
A missing title, a blocked page or links search engines cannot follow are simple to fix and worth fixing. A perfect score here does not guarantee rankings; useful content still matters most.
Missing labels, low contrast and unnamed buttons are found automatically. Keyboard use, screen reader flow and clear wording need a person to test them.
Why a website feels slow
The report points to a problem; the page and its loading sequence tell you what to change. Check the affected URL on mobile first, then compare desktop if that is where your customers work.
Look at the largest visible image or text block. A slow server response, oversized hero image, late-loading font or render-blocking code can delay it. Use the Lighthouse opportunities to identify the actual bottleneck before changing the design.
Long JavaScript tasks and busy third-party scripts can hold up a response to a tap. If real-visitor INP is available, inspect the slow interaction on the page and reduce the work it triggers.
Images without reserved space, late banners and changing font sizes can move buttons or text after a visitor starts reading. Reserve space for media and test dynamic sections on a phone.
Lighthouse can flag missing titles and other basic issues. It cannot tell you whether the page answers the right search, earns trust or will rank. Review the page's content and Search Console queries as well.
The PageSpeed Insights documentation explains field and lab data. Its Core Web Vitals guidance uses LCP, INP and CLS to describe loading, responsiveness and visual stability.
About this check
This check looks at one page at a time. Test your homepage and the page most visitors land on from search or ads.
Server response, ads, third-party scripts and network conditions change between runs. A few points of difference is normal. Look at the trend and at the issues listed, not a single number.
No. A page in the green range with good real-visitor data is doing its job. Chasing the last few points can cost more than it is worth, especially if it means removing tools your team relies on.
Usually, yes, though how much depends on the platform. Image sizes, plugins, third-party scripts and theme code are the common causes, and most can be improved without a rebuild.
The address is sent to Google PageSpeed Insights, which loads the public page to test it. This website does not store it. Nothing is sent to me unless you use the form below the report.
No. The test loads the page as a new visitor would, so it can only check publicly available pages.
Optional
I'm Hasnain Qureshi, a full-stack developer working with Next.js, WordPress, React and Node.js. My work includes Cambridge Research Park and The New 1540 Broadway.
Send the report and I'll reply with what I'd fix first and roughly what it involves. There's no obligation. Planning a rebuild instead? Use the website cost calculator and website brief builder.