Website speed test,free, no sign-up.

A measurement of how long your website takes to become usable, not to finish loading. This test opens your page on a simulated phone with a 4G connection and measures when the content appears, how much the page shifts while loading and how long the phone stays frozen, unable to respond to a tap. The final score runs from 0 to 100 and is calculated by Lighthouse, Google's engine.

Google uses three bands: 90 to 100 in green, 50 to 89 in orange and below 50 in red. That orange band is too wide, because it paints a website scoring 87 the same as one scoring 52, and they are nothing alike. In this test the score is exactly Google's, but the colour counts as green from 75, for every website alike. Below 50 it is almost always unoptimised images, templates loaded with features nobody uses and too many plugins.

Because it is the one that counts. Google has indexed and ranked the mobile version of websites since 2019, and that is where most traffic arrives. It is also the tougher measurement: phones have weaker processors and worse networks, so a website that passes on mobile passes anywhere. Showing the desktop score next to the mobile one only serves to dress up the result.

Because you already have it cached, you open it on your wifi and probably on a better phone than average. The test starts from zero every time, with the network and processor deliberately limited to resemble a first-time visitor out on the street. That visitor is the one who leaves if it is slow.

It is the category Google added to PageSpeed Insights to measure whether an AI agent can read your website. ChatGPT, Claude, Gemini and Perplexity already recommend businesses, and to cite yours they need to understand the page without running all of it: a well-formed accessibility tree, a stable structure and, if you have one, an llms.txt file. If that score is incomplete, your website exists for Google but is invisible to AI answers.

In order of impact: serve images in a modern format and at the size they are displayed, remove JavaScript that is not used (almost always plugins and legacy libraries), host fonts on your own domain instead of loading them from Google, and reserve space for each block so the page does not jump while loading. On a template-based website there is usually a ceiling: at some point what needs removing is the template.