Lighthouse is an open-source tool built into Chrome DevTools that audits web pages across four categories: Performance, Accessibility, Best Practices, and SEO. Each gets a score from 0-100. It's become the default benchmark teams chase — and that's both its greatest strength and its biggest trap.
The performance score is a weighted composite of six metrics: FCP, LCP, TBT, CLS, Speed Index, and Time to Interactive. Here's what most people don't realize: Lighthouse runs in a simulated throttled environment, not real-world conditions. Your lab score of 95 might correspond to a real-user performance that's significantly worse if your visitors are on slower devices or connections than Lighthouse simulates.
When Lighthouse helps vs. when it misleads
Lighthouse is excellent for catching specific issues: missing alt text, render-blocking resources, uncompressed images, missing meta descriptions. Each audit gives you a concrete, fixable recommendation. Use it as a diagnostic checklist, not a scoreboard.
Where it misleads: teams obsess over hitting 100 while ignoring what actually drives conversions. A page with a Lighthouse performance score of 72 that loads fast on real devices and converts well is better than a page scoring 98 that has no compelling value proposition. I've seen teams spend weeks squeezing out 5 Lighthouse points while their conversion copy was terrible. Fix the words first, then optimize the pixels and milliseconds.