Understanding Lighthouse Scoring
Demystify how Lighthouse turns raw measurements into the 0-100 Performance score, including metric weights, scoring curves, and why your score can fluctuate.
Understanding Lighthouse Scoring is a free Web Performance Optimization & Lighthouse lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Web Performance Optimization & Lighthouse learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What the Number Means
The Lighthouse Performance score is a 0-100 summary of several lab metrics. It is a weighted blend, not a single measurement, so improving one metric does not always move the score the same amount.
The Weighted Metrics
The score is built from a handful of metrics, each with a weight. The biggest contributors are typically Largest Contentful Paint, Total Blocking Time, and Cumulative Layout Shift.
Metric Weights
In recent Lighthouse versions the approximate weights are: TBT 30%, LCP 25%, CLS 25%, FCP 10%, Speed Index 10%. Heavier-weighted metrics move the score most.
Each Metric Gets a Score
Every raw metric value is first mapped to its own 0-100 sub-score using a log-normal scoring curve derived from real-world data. The weighted average of these sub-scores is the final number.
The Scoring Curve
The curve is non-linear. Near the fast end, shaving milliseconds barely helps; in the middle, the same improvement can jump your score several points. This is why mid-range pages see big gains from small fixes.
Color Bands
- 0-49 red (poor)
- 50-89 orange (needs improvement)
- 90-100 green (good)
Aim for green, but treat the bands as guidance, not a finish line.
Lab vs Field
Lighthouse runs in a lab: a single simulated load on throttled hardware. Real users vary by device and network, so lab scores are a controlled proxy, not exact field data.
Why Scores Fluctuate
Variance comes from network jitter, background CPU, A/B tests, and third-party scripts. Run audits multiple times and look at the median rather than a single run.
Reading the Calculator
Lighthouse reports link to a scoring calculator. Paste your metric values to see how each contributes and simulate the impact of a fix before you build it.
Don't Chase 100
A perfect 100 is rarely worth the effort. Focus on getting heavy-weighted metrics into the green and on real user experience over the vanity number.
Practical Strategy
- Target TBT and LCP first (highest weight).
- Run 3-5 audits, use the median.
- Use the calculator to prioritize fixes.
- Validate against field data when possible.
Quick Check
Two pages improve a metric by the same amount, but their scores change differently. Why?
Recap
You learned the Lighthouse Performance score is a weighted blend of metric sub-scores, mapped through a non-linear curve, run in a lab environment. Focus on heavy-weighted metrics, use medians, and prioritize with the scoring calculator.
Frequently asked questions
Is the “Understanding Lighthouse Scoring” lesson free?
Yes — the full text of “Understanding Lighthouse Scoring” is free to read here on the web, and the Web Performance Optimization & Lighthouse course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Web Performance Optimization & Lighthouse course, upgrade to CoddyKit PRO.
What will I learn in “Understanding Lighthouse Scoring”?
Demystify how Lighthouse turns raw measurements into the 0-100 Performance score, including metric weights, scoring curves, and why your score can fluctuate. You practise Web Performance Optimization & Lighthouse with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Web Performance Optimization & Lighthouse?
No prior experience is required. Web Performance Optimization & Lighthouse on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Understanding Lighthouse Scoring” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Web Performance Optimization & Lighthouse lesson?
Yes. Every Web Performance Optimization & Lighthouse lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Introduction to Google Lighthouse
- Running Your First Audit
- Interpreting Lighthouse Reports
- Understanding Lighthouse Scoring