Your website has a score between 0 and 100 that Google uses to evaluate it. Most business owners have never seen it. Of those who have, most have scores that would concern them if they understood what they were looking at.
Google Lighthouse is an open-source tool built into Chrome and available at pagespeed.web.dev. It measures how fast your site loads, how stable the layout is, and how quickly a user can interact with it. The score isn’t just a vanity metric — it directly influences your search rankings and your conversion rate.
What Lighthouse Actually Measures
Lighthouse generates four category scores: Performance, Accessibility, Best Practices, and SEO. Each runs from 0 to 100. When people talk about “your Lighthouse score,” they typically mean the Performance score — the one directly tied to page speed.
The Performance score is a weighted average of six metrics. Three of them — the Core Web Vitals — carry the most weight and have direct SEO implications.
Largest Contentful Paint (LCP) — 25% of Score
LCP measures how long it takes for the largest visible element on your page to fully render. That’s usually your hero image, headline, or main content block.
Google’s thresholds:
- Good: under 2.5 seconds
- Needs improvement: 2.5–4 seconds
- Poor: over 4 seconds
Most business websites fall in the 3–6 second range for LCP on mobile. The primary culprits: large unoptimized images, render-blocking fonts, and excessive CSS stylesheets that delay rendering.
Total Blocking Time (TBT) — 30% of Score
TBT measures how long your page is unresponsive to user input while JavaScript executes. A blocked page is one where clicking a button, filling a form field, or navigating doesn’t work — the browser is busy processing scripts.
Google’s thresholds:
- Good: under 200ms
- Needs improvement: 200–600ms
- Poor: over 600ms
Page builders are the primary cause of high TBT. Elementor regularly produces 800–1,200ms of blocking time. Excessive third-party scripts (chat widgets, ad trackers, analytics not loaded asynchronously) also contribute significantly.
Cumulative Layout Shift (CLS) — 15% of Score
CLS measures how much your page layout shifts unexpectedly as it loads. If you’ve ever clicked a button on a page that suddenly jumped because an ad loaded above it — that’s a CLS failure.
Google’s thresholds:
- Good: under 0.1
- Needs improvement: 0.1–0.25
- Poor: over 0.25
CLS is caused by images without specified dimensions, fonts that swap after initial render, and dynamically injected content. Most WordPress sites with poor CLS are loading web fonts without proper font-display settings.
First Contentful Paint (FCP) — 10% of Score
FCP measures when the browser first renders any content — text, images, or the page background. It’s a proxy for “when does the user see something is happening.”
A slow FCP means users are staring at a blank page. The main causes are slow server response time (Time to First Byte), render-blocking resources, and poor hosting.
Speed Index and Time to Interactive (TTI)
Speed Index measures how quickly content visually populates the page. Time to Interactive measures when the page is fully functional for user input. Both are weighted in the score but are often improved as byproducts of fixing the Core Web Vitals above.
What a Good Score Actually Looks Like
The scoring tiers:
- 90–100: Fast. Google considers this a positive performance signal.
- 50–89: Needs improvement. Competitive disadvantage in search results.
- 0–49: Slow. Significant ranking impact and high bounce rates.
The average Lighthouse mobile score for a WordPress site in 2024 was approximately 55. For sites built with Elementor or Divi, the average drops to 35–42. For sites built by hand with no page builders, 90+ is achievable and maintainable.
Designodin builds to a Lighthouse floor of 90+ on mobile for every project. That’s not marketing language — it’s a specification. You can verify any site’s score at honest.designodin.com.
Mobile vs. Desktop Scores
Lighthouse runs two audits: mobile and desktop. Desktop scores are almost always 15–25 points higher than mobile scores, for the same site.
Mobile Lighthouse simulates a mid-range device on a 4G connection — not a flagship phone on WiFi. This is intentional. It reflects how most users actually browse the web. Google uses mobile performance as its primary ranking signal.
Business owners who only check desktop scores are optimizing for the wrong benchmark. If your mobile score is 60 and your desktop score is 85, your site is performing poorly for most of your audience.
What Hurts Your Lighthouse Score Most
The five most common causes of poor scores, in rough order of impact:
1. Large, uncompressed images. A hero image over 1MB adds 2–4 seconds to LCP on mobile. The fix is compression (70–80% quality) and modern formats (WebP instead of JPEG or PNG).
2. Page builder JavaScript and CSS. Elementor, Divi, and equivalents add 400–800KB of scripts that block rendering. There’s no plugin fix for this — the overhead is structural.
3. Render-blocking scripts and styles. Third-party scripts (Google Tag Manager, Facebook Pixel, Intercom, Drift, Zendesk) each add blocking time when loaded synchronously. Load them asynchronously or defer them.
4. Slow hosting. If your server takes 600ms to respond to the first request, that’s 600ms before the browser has loaded any content. Managed WordPress hosts (Kinsta, WP Engine, Cloudways) typically deliver Time to First Byte under 200ms.
5. Excessive plugins. Each WordPress plugin can add scripts, stylesheets, and database queries. A site with 40 active plugins carries more overhead than one with 12, even if individual plugins seem lightweight.
How Lighthouse Score Affects SEO
Google confirmed Core Web Vitals as a ranking signal in 2021 as part of the “Page Experience” update. The signal doesn’t operate as a binary pass/fail — it’s a relative competitive factor.
In practice: if two pages compete for the same keyword and have similar content quality, the faster page has a ranking advantage. In competitive niches, that advantage is measurable. In low-competition niches, other factors dominate and the impact is smaller.
What’s definitively true: a Lighthouse score below 50 signals to Google that your page provides a poor user experience. That never helps rankings. It also increases your bounce rate — users leave slow pages before converting, which compounds the SEO problem with a conversion problem.
How to Check Your Score
Three ways, in order of accuracy:
PageSpeed Insights (pagespeed.web.dev) — Uses real-world Chrome user data combined with lab tests. More accurate than running Lighthouse locally because it reflects actual user conditions.
Chrome DevTools Lighthouse — Open Chrome, right-click, Inspect, then the Lighthouse tab. Useful for testing local or staging sites, but results vary by your machine’s CPU and connection speed.
honest.designodin.com — Runs a full performance and SEO audit, presenting the results with context about what matters most for your specific site.
Run the audit on mobile, not desktop. Check your most important landing pages — homepage, top service page, or highest-traffic blog post. Fixing those pages first gets you the most SEO and conversion return.
FAQ
Does a good Lighthouse score guarantee better Google rankings? No. It removes a disadvantage. Content quality, backlinks, on-page optimization, and domain authority all matter more than performance in most situations. But poor performance creates a ceiling on how well those other factors can work.
My site scores 65 on desktop but 40 on mobile. Which one matters? Mobile. Google indexes mobile-first and uses mobile performance as its ranking signal. The desktop score is largely irrelevant for SEO purposes.
How often should I check my Lighthouse score? After any significant site change — new plugin, theme update, major content addition. Also monthly as a baseline check. Scores drift over time as plugins update and add overhead.
Can I improve my Lighthouse score without rebuilding the site? Yes, partially. Image compression, script deferral, and caching plugins can move a score from 40 to 60–65. Getting from 65 to 90+ usually requires removing the structural overhead (page builders, excessive plugins) that can’t be patched around.
What is a passing Core Web Vitals score? Google defines passing as: LCP under 2.5s, FID/INP under 200ms, and CLS under 0.1 — all measured at the 75th percentile of page loads. All three must pass for Google to consider your page’s performance “good.”
Does Lighthouse measure the same thing as bounce rate? No, but they’re correlated. Lighthouse measures technical performance. Bounce rate measures user behavior. Slow sites have high bounce rates — users leave before the page loads. But bounce rate is also affected by content relevance and user intent, which Lighthouse doesn’t measure.
How do I know if my slow score is a hosting problem or a code problem? Check Time to First Byte (TTFB) in Lighthouse’s diagnostics. If TTFB is over 600ms, hosting is your primary bottleneck. If TTFB is under 400ms but your score is still poor, the problem is in the page’s code and assets.
If your Lighthouse score is under 70 on mobile, there’s revenue and search visibility being left behind. Start with a free audit at honest.designodin.com. If the audit shows structural problems that plugins can’t fix, that’s when a hand-coded WordPress rebuild becomes the right conversation. Get started and we’ll scope what’s needed.