May 24, 2026 · 6 min read
How to Read Your Google Lighthouse Score (Without Being a Developer)
You ran the grader, saw 'Lighthouse mobile: 31', and panicked. Here's what each Lighthouse number actually means, in language that does not assume you write code.
If you ran your site through the ostra.studio/grade tool, you saw two Lighthouse scores - one for mobile, one for desktop. If your mobile score was under 50 (most local sites are), you probably panicked a little. This is a quick guide to what Lighthouse is actually measuring, what each number means, and which ones a small business should care about.
What Lighthouse is
Lighthouse is Google's free site-audit tool. It loads your page in a real browser on a simulated slow phone, measures how long things take, and gives you a score between 0 and 100. Higher is better. The grader pulls both the mobile and desktop scores live from Google's servers - it's the same audit Chrome runs when you click 'Lighthouse' in DevTools.
What the score actually scores
Lighthouse rolls up several individual metrics into one number. The big three for performance are LCP, CLS, and TTI. Those are the ones you'll see in the grader result.
LCP stands for Largest Contentful Paint. Translation: how long until the biggest thing on the page (usually your hero image or a big heading) finishes loading. Under 2.5 seconds is good. Over 4 seconds is bad. Customers leave at about second 3.
CLS stands for Cumulative Layout Shift. Translation: how much your page jumps around while it loads. You know when you go to tap a button and the page suddenly shifts and you tap the wrong thing? That's high CLS. Under 0.1 is good. Over 0.25 is bad.
TTI stands for Time to Interactive. Translation: how long until the page stops being a static picture and actually responds to taps. Under 3.8 seconds is good. Over 7 seconds is bad.
What the score does NOT measure
Important: Lighthouse does not score how good your design is, how clear your copy is, or whether your site closes sales. It only measures technical performance. A site can score 100/100 on Lighthouse and still suck at converting visitors into customers. A site can score 40/100 and still sell hard because the offer is right.
Lighthouse is a useful technical floor. It is not the whole picture. Treat it as one input among many.
Why most local sites score badly on mobile
Local business sites tend to score 30 to 50 on mobile Lighthouse. The reasons are pretty consistent:
First reason: uncompressed images. A homepage hero shot that's 4MB instead of 200KB will tank your LCP every time. Most non-developers upload images straight from a phone or a stock site without compressing. The fix is free: TinyPNG, Squoosh, or any image-compression tool. Upload at 200-400KB per image, not 2-4MB.
Second reason: too many third-party scripts. Google Tag Manager loading Facebook Pixel loading Hotjar loading a chat widget loading an SEO tool. Each script adds 100-500ms to your TTI. The fix is to audit what you actually need and remove the rest. Most small business sites only need Google Analytics and maybe one form tool.
Third reason: cheap WordPress hosting. Bluehost, GoDaddy shared hosting, anything advertising 'unlimited everything for $3/month'. These hosts cram thousands of sites onto one server. Your server response time on these is usually 2-4 seconds before your page even starts loading. Modern hosting (Vercel, Cloudflare Pages, even a $20/mo VPS) is 100-300ms.
Fourth reason: builder-platform bloat. Wix, Squarespace, GoDaddy Website Builder, Weebly. These platforms add 200-500KB of platform CSS and JavaScript to every page whether you use it or not. Your homepage might have 50KB of actual content under a megabyte of platform overhead. You cannot fully fix this without changing platforms.
What 'good' looks like for a local business
You do not need a 100. You need a 75 on mobile and a 90 on desktop. That gets you out of the danger zone where Google might rank you lower for site speed and where mobile visitors bounce before the page loads.
Brutal honest version: if your mobile Lighthouse score is under 50, fixing it is the highest-leverage thing you can do for your site. It's typically 2 to 5 hours of work and the impact on bounce rate is enormous. If your score is 55-75, you have room to improve but it's not on fire. If your score is 80+, focus your time on design + copy + conversion, not chasing the last 20 Lighthouse points.
The order to fix things in
If you only have a Saturday: First, compress every image on your site. Second, check that lazy-loading is on for any image below the fold (most modern platforms do this by default - check yours). Third, audit your third-party scripts and remove anything you do not actively use. That alone usually adds 20-30 points to mobile.
If that's not enough: the platform is probably the problem. Custom-built sites (what I do at Ostra) score 90+ on mobile out of the box because the platform has nothing to bloat. Wix and Squarespace sites usually plateau in the 50-65 range no matter what you do, because the platform itself is the bottleneck.
The grader
Drop your URL into ostra.studio/grade and you'll see your real Lighthouse mobile + desktop scores, plus a stack of other checks the grader runs in parallel. No signup, no follow-up nag. If your scores embarrass you, the result page has a fix list ordered by impact.