A Lighthouse score is the grade Google’s free Lighthouse tool gives a web page, from 0 to 100, across four areas: performance, accessibility, best practices and SEO. It runs the page through a series of checks and tells you, in plain numbers, where it stands and what to fix.
Think of it like a vehicle inspection. The page is your car, and Lighthouse is the test bay that checks the brakes, lights and emissions, then hands you a report card with the failures listed. You do not have to guess what is wrong; the report points right at it. The performance section leans heavily on the same Core Web Vitals and load time that Google watches.
The report goes beyond a single number. Under each category it lists specific opportunities, like “serve images in next-gen formats” or “reduce unused JavaScript”, with an estimate of how many milliseconds each fix would save. That turns a vague “make it faster” into a ranked to-do list. You can run it from the Chrome DevTools panel, the command line, or a build pipeline so a pull request fails when the score drops.
A common mistake is treating the four scores as one. They are not connected; a page can score 100 on SEO and 40 on performance at once, because each category measures something different. So read them separately and fix the one that matters for the page in front of you.
One thing to keep in mind: the score moves depending on the device and connection you test from, so a single run is a snapshot, not a verdict. Field data from real visitors, which feeds the Largest Contentful Paint numbers Google actually ranks on, tells a fuller story than one lab run. The advice it gives matters more than the exact number.
At TopDevs we use Lighthouse as a checklist throughout a build, fixing what it flags so a site ships fast, accessible and search-ready rather than chasing the number alone.
