grEEff.dev
WorkProcessPricingInsights
Start Your Project
Engineering

February 15, 2025

12 min

Understanding Google Lighthouse Scores: The Complete Guide to Web Performance

A deep dive into how Lighthouse measures your website, what each score means, and proven strategies to achieve 90+ across all four categories.

Pio Greeff

Pio Greeff

Founder & Lead Developer

Deep dive article

Introduction: Why Lighthouse Scores Matter

In the modern web, performance is not a luxury—it is a competitive advantage. According to Google's research, a 1-second delay in page load can result in a 7% reduction in conversions, an 11% decrease in page views, and a 16% drop in customer satisfaction.

Every 100ms of latency costs Amazon 1% in sales. For a company that size, that translates to billions in lost revenue annually.

Google Lighthouse is an open-source, automated tool for measuring the quality of web pages. It audits performance, accessibility, best practices, and SEO, providing actionable insights that directly impact your search rankings, user experience, and bottom line.

This guide will teach you everything you need to know about Lighthouse: how it works, what each metric means, and concrete strategies to improve your scores.


Part 1: The Four Pillars of Lighthouse

Lighthouse evaluates your website across four key categories, each scored from 0 to 100. Here is what optimal performance looks like:

Core Web Vitals

Performance metrics for SEO

PASSED

Largest Contentful Paint

LCP

1.8

s

Good

Interaction to Next Paint

INP

120

ms

Good

Cumulative Layout Shift

CLS

0.03

Good

And here is what poor performance looks like—the kind of scores that actively hurt your business:

Core Web Vitals

Performance metrics for SEO

Largest Contentful Paint

LCP

4.5

s

Poor

Interaction to Next Paint

INP

450

ms

Needs Work

Cumulative Layout Shift

CLS

0.28

Poor

Let us break down each category.

Performance (Green: 90-100, Orange: 50-89, Red: 0-49)

The Performance score measures how quickly your page loads and becomes interactive. It is calculated using a weighted average of six metrics:

MetricWeightDescription
First Contentful Paint (FCP)10%Time until the first text or image is painted
Largest Contentful Paint (LCP)25%Time until the largest content element is visible
Total Blocking Time (TBT)30%Sum of time the main thread was blocked
Cumulative Layout Shift (CLS)25%Measures visual stability during load
Speed Index10%How quickly content is visually displayed

According to web.dev's scoring documentation, the weights are designed to prioritize metrics that most closely correlate with perceived user experience.

TBT carries the highest weight (30%) because blocking JavaScript is the primary killer of interactivity on modern websites.

Target Thresholds:

  • LCP: Under 2.5 seconds
  • FID/TBT: Under 100ms / 200ms
  • CLS: Under 0.1

Accessibility

The Accessibility score evaluates how well your site can be used by people with disabilities. Lighthouse runs over 50 automated checks based on the Web Content Accessibility Guidelines (WCAG).

Common Issues That Tank Scores:

  • Missing alt attributes on images
  • Insufficient color contrast (less than 4.5:1 ratio)
  • Missing form labels
  • Improper heading hierarchy
  • Non-descriptive link text ("click here")

A WebAIM study of the top 1 million websites found that 96.8% of home pages had detectable WCAG 2 failures. Accessibility is not a feature—it is a legal and ethical requirement.

Best Practices

This category covers a range of security, modern web development, and user-trust indicators:

  • HTTPS usage — Pages served over secure connections
  • Console errors — JavaScript errors in the browser console
  • Deprecated APIs — Use of outdated browser features
  • Image aspect ratios — Correctly sized images to prevent layout shift
  • Password field security — Proper autocomplete attributes

SEO

The SEO score verifies that your page follows basic search engine optimization guidelines:

  • Has a <title> element
  • Has a <meta name="description">
  • Uses legible font sizes
  • Has a valid robots.txt
  • Links are crawlable
  • Page is mobile-friendly

While Lighthouse's SEO checks are relatively basic, they cover the foundational requirements. For advanced SEO, tools like Ahrefs or Screaming Frog provide deeper analysis.


Part 2: How Lighthouse Actually Works

Understanding the mechanics helps you interpret and debug results more effectively.

The Testing Environment

Lighthouse simulates a mid-tier mobile device on a throttled 4G connection by default:

SettingValue
CPU Throttling4x slowdown
Network150ms RTT, 1.6Mbps download
Device EmulationMoto G4 equivalent

This explains why your scores in Lighthouse are often lower than what you see on your MacBook Pro with gigabit fiber. Lighthouse is testing the experience for the average user, not the developer.

Variability in Scores

Lighthouse scores can fluctuate between runs due to:

  • Network variability
  • Server response time changes
  • Third-party script behavior
  • CDN caching state

Google recommends running Lighthouse 3-5 times and taking the median, or using PageSpeed Insights which provides field data alongside lab data.


Part 3: Proven Strategies to Improve Each Score

Boosting Performance

1. Optimize Images

Images are often the largest payloads. Use modern formats and responsive sizing:

2. Minimize JavaScript

Large JavaScript bundles block the main thread. Strategies include:

  • Code splitting with dynamic imports
  • Tree shaking unused code
  • Deferring non-critical scripts

3. Use a CDN

Content Delivery Networks like Cloudflare or Vercel Edge Network cache assets at edge locations, reducing latency dramatically.

4. Implement Caching

Set appropriate Cache-Control headers:

For static assets that rarely change, this allows browsers to skip network requests entirely.

Improving Accessibility

1. Run axe DevTools

The axe browser extension provides more detailed accessibility auditing than Lighthouse alone.

2. Use Semantic HTML

3. Ensure Keyboard Navigation

All interactive elements must be reachable and operable via keyboard. Test by tabbing through your entire page.

Fixing Best Practices

  • Serve all resources over HTTPS
  • Fix JavaScript console errors
  • Avoid document.write()
  • Use passive event listeners for scroll/touch

Optimizing SEO

  • Unique <title> and <meta description> for each page
  • Proper heading hierarchy (one <h1> per page)
  • Mobile-friendly viewport: <meta name="viewport" content="width=device-width, initial-scale=1">
  • Descriptive image alt text
  • Structured data markup (JSON-LD)

Part 4: Tools for Continuous Monitoring

Lighthouse is a point-in-time audit. For production monitoring, consider:

ToolPurpose
PageSpeed InsightsLab + field data from real Chrome users
Lighthouse CIRun Lighthouse in your CI/CD pipeline
Web Vitals LibraryMeasure Core Web Vitals in production
SpeedCurveContinuous performance monitoring

Part 5: What Scores You Should Target

The question we hear most often: "What's a good score?"

Our recommendation for business websites:

CategoryTargetWhy
Performance90+Directly impacts bounce rate and conversions
Accessibility100Legal liability (ADA) and inclusive design
Best Practices90+Security and modern web standards
SEO95+Foundation for organic discoverability

Achieving perfect 100s across all categories is often impractical due to third-party scripts, dynamic content, and CMS limitations. The goal is sustainable excellence, not perfection theater.

We target 90+ and verify with real-user monitoring.


Conclusion: Performance as a Feature

Lighthouse scores are not just vanity metrics. They correlate directly with business outcomes:

  • Conversion rates improve with faster load times
  • SEO rankings favor performant, accessible sites
  • User trust increases with secure, well-built experiences

At grEEff.dev, we treat performance as a first-class product feature. Every site we launch targets 90+ Lighthouse scores, verified across multiple runs and real-world conditions.

Want to see how your current site scores? Run a free audit at PageSpeed Insights and reach out if you would like help closing the gap.


Further Reading

Found this useful?

Share it with your network

Starter Kits

Build the architecture behind this article

Ship faster with production-ready Next.js + Cloudflare starter kits. Pick one path, or take the full bundle.