Lighthouse is a free tool made by Google that grades any web page. It’s the engine behind PageSpeed Insights and it’s built into the Chrome browser. You give it an address, it loads the page the way a visitor would, and it hands back four scores out of 100 plus a list of everything it found.
I put the score on my homepage and on every project in my gallery because it’s the one claim about a website that anyone can check in under a minute. This article explains what you’re looking at when you do.
The four scores
Each one is a separate test, and they don’t depend on each other. A page can be fast and inaccessible, or accessible and slow.
- Performance is how quickly the page shows up and becomes usable. This is the one people mean when they say “our Lighthouse score.” It’s also the hardest to get right and the one that moves the most between tests.
- Accessibility checks whether people using screen readers, keyboards or zoomed-in text can use the page: labelled buttons, enough colour contrast, images with descriptions, headings in a sensible order.
- Best Practices is a list of things a well-built site should and shouldn’t do: serving everything over HTTPS, no errors in the browser console, no outdated or insecure code, images shown at a sensible resolution.
- SEO checks the basics that let Google understand the page: a title and description, text that’s readable on a phone, links that can be followed, nothing blocking the crawler. It’s a floor, not a ranking guarantee.
How the performance score is calculated
The performance number isn’t one measurement. It’s five, each weighted differently, combined into a score. Three of them do most of the work.
So 80% of the performance score comes from three things: does the page respond to taps, does the main content show up quickly, and does it hold still. That’s why a site can look fine and still score in the 40s. The visitor sees a page; Lighthouse sees three seconds of frozen scripts underneath it.
One more thing worth knowing: the phone test is run on a simulated mid-range phone over a slow connection. That’s deliberate. It’s not your phone on your office Wi-Fi, it’s a customer in a parking lot with two bars. The desktop test is far more forgiving, which is why the two numbers are often 30 points apart.
What the colours mean, and where most sites land
Lighthouse colours every score the same way:
- 0 to 49, red: poor.
- 50 to 89, orange: needs improvement.
- 90 to 100, green: good.
Most small-business websites are orange or red on the phone test. Not because their owners did anything wrong, but because the platforms they’re built on are heavy. The HTTP Archive measures millions of sites every year, and the median mobile performance score on the big website platforms sits between 30 and 59.
Why the number matters
Three reasons, in order of how much they’ll affect you.
- People leave slow pages. The BBC found it lost 10% of its visitors for every extra second a page took. Vodafone made its main content appear 31% faster and sold 8% more. These are big companies with big budgets to measure such things; the same behaviour applies to a plumber’s site, it just goes unmeasured.
- Google uses it. The three heaviest metrics above (loading, responsiveness, stability) are Google’s “Core Web Vitals,” and Google has said page experience is part of how it ranks results. It won’t lift a bad page above a good one, but between two similar pages, the faster one has the edge.
- Ads cost more on slow pages. Google Ads rates the experience on your landing page, and speed is part of that rating. A worse rating means paying more per click for the same position.
Sources: web.dev, Why speed matters; Google Search Central on page experience.
Why the number changes every time you run it
Run the test three times and you may get 71, 68 and 74. That’s normal. Lighthouse loads the page on a simulated connection and a real server, and both vary from second to second. Google’s own documentation says to treat the score as a range rather than a single number.
What that means in practice: a site that scores 95 one minute and 92 the next is a 90s site. A site that scores 48 then 55 is a 50s site. Don’t chase the last few points; the difference between 97 and 100 is noise. The difference between 45 and 90 is not.
At the top of a PageSpeed Insights report there’s also a section called “Discover what your real users are experiencing.” That’s field data from actual Chrome visitors over the last month, if the site gets enough traffic to have any. Lab scores tell you what’s wrong; field data tells you whether it’s hurting.
What a 100 doesn’t tell you
I care about this score, so I want to be straight about its limits.
- It doesn’t measure whether the site is good. Ugly, confusing pages can score 100. The score says the page is fast, usable and well built, not that anyone will call you.
- An accessibility score of 100 means the automated checks passed. Roughly a third of accessibility problems can’t be found by a machine; someone still has to tab through the page and try it with a screen reader.
- It tests one page at a time. A fast homepage with a slow contact page is a slow site where it counts.
- It can be gamed. There are tricks that fool the test without helping visitors. If a site scores 100 but feels slow, trust your thumb.
Go to pagespeed.web.dev, paste in any address, and read the phone result. Try your own site, then try gbfm.dev and anything in my gallery. Then try your competitors. It takes a minute each and it tells you more than any sales pitch.
How to read your own report
- Look at the four scores on the phone tab. Write them down with today’s date so you have a before.
- Scroll to the metrics. Find Largest Contentful Paint. Under 2.5 seconds is good; over 4 is where visitors give up.
- Read the “Diagnostics” list. The first few items, usually about images, scripts and fonts, are where the time is going. This article walks through each one.
- Ignore the tiny stuff until the big three are fixed. A 20-millisecond saving doesn’t matter when images are costing you four seconds.
- Re-test after every change. Three runs, take the middle one.
The score isn’t the point. A customer who didn’t leave is the point. The score is just how you know.
Want me to look at your site?
Send me the address and I’ll tell you what’s slowing it down, what it’s missing, and what I’d fix first. No charge, no pressure.