Website speed test: find what makes your page slow and fix it first

Yes, but as one signal among many. Google uses Core Web Vitals, measured on real Chrome visitors, as part of its page experience signals, and a relevant page still beats a faster one that answers the query less well. Speed matters even more to people: slow pages lose visitors before they see anything, most of all on phones. Pass the three Core Web Vitals first; this test shows whether you do.

90 or above is good, 50 to 89 needs improvement and below 50 is poor, on Lighthouse's 0-100 performance score. Mobile scores are usually much lower than desktop, because the test simulates a mid-range phone on a slow connection. The score is a lab summary; for ranking, Google uses real-user Core Web Vitals, which the test shows beside it.

Enter the page address above and pick mobile or desktop. The test runs Google Lighthouse through the PageSpeed Insights API and adds real-visitor Core Web Vitals from the Chrome UX Report, usually in under a minute. Test your home page and your most important templates, such as a product or article page, because each template has its own weight and its own problems.

Usually because of a few heavy things, not the whole site. The common causes are images uploaded at camera size, stylesheets and scripts that block rendering, third-party tags such as chat widgets and trackers, and a server that takes over 600 ms to answer. The filmstrip shows when content appears, the request waterfall shows what loaded when, and each finding names the file responsible.

Yes. Above the filmstrip you get the page size, the number of requests, and when the page was ready, loaded and fully loaded, with the weight split by type of file and by domain. The waterfall lists every request. The three times come from Google's test browser before it simulates a slower phone, so they run faster than the scored timings; GTmetrix and Pingdom test from their own locations, so their numbers differ too.

The lab numbers are the same Lighthouse run, because we call Google's API. Around it you get a plain-language fix for every finding, the other six modules, a shareable link that stays live for 12 months, PDF and JSON export, and history when you test again. For many pages at once, use the bulk PageSpeed checker.

Lab numbers come from one throttled run in a data centre; field numbers are the 75th percentile of real Chrome visitors over 28 days. Real users have different phones and networks from the lab's throttled profile, so treat the field numbers as the truth and the lab as the diagnosis. Google ranks on the field numbers.

Yes, with no sign-up. getReport is funded by donations, not plans, and the complete report with all seven modules is one click away, also free. It stays at its shareable link for 12 months, is not listed publicly and carries a noindex tag, and nothing about your visitors is collected.