Meta-Scan

AI-Friendly AEO & GEO & SEO Analyzer

Blog
ONLINE
Support
© 2026 Meta-Scan. All rights reserved.
BlogAboutPrivacy PolicyTerms of Service
SYSTEM ONLINE
Home/Blog

Improving Your Lighthouse Score: What to Fix First

Yuuuk94·Published 2026-11-12

Summary

Lighthouse is Google's page audit tool. It scores performance, accessibility, best practices and SEO from 0 to 100. Chrome DevTools, PageSpeed Insights and META_SCAN's results screen all run the same engine.

The fastest way to raise the performance score is to start with the heaviest-weighted metrics. Total Blocking Time (TBT), Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS) make up 80% of it.

01How the performance score is calculated

MetricMeaningWeight
TBT (Total Blocking Time)Total time the main thread was blocked and couldn't respond to input30%
LCP (Largest Contentful Paint)When the largest element on screen (often the hero image or heading) rendered25%
CLS (Cumulative Layout Shift)How much content moved around while loading25%
FCP (First Contentful Paint)When the first text or image rendered10%
Speed IndexHow quickly the screen fills in10%

Weights are for Lighthouse 10. Get TBT, LCP and CLS under control and most of the score follows. Shaving FCP alone barely moves it.

02Priority 1: reduce LCP

The LCP element is usually the hero image. If it is discovered late, is too large, or waits behind other resources, LCP suffers.

  • Don't lazy-load the hero image: loading="lazy" on an above-the-fold image makes it later. Use fetchpriority="high" instead.
  • Size and format: resize to the displayed size and switch to WebP or AVIF. Use srcset for different devices.
  • Discoverable in the HTML: CSS background images and images injected by JavaScript are found late by the browser.
  • Server response time: if the first HTML arrives late, every metric slips with it. Check caching and your CDN.

03Priority 2: reduce TBT

TBT grows when JavaScript holds the main thread for long stretches. It is the most common reason framework-based sites score poorly.

  • Remove unused JavaScript. Lighthouse's "Reduce unused JavaScript" audit lists the waste per file.
  • Load heavy libraries dynamically, only on the screens that need them.
  • Defer third-party scripts such as ads, analytics and chat widgets with async/defer, or until user interaction.
  • Move what can be server-rendered to server components so less code ships to the client.

From experience

When I improved a product using Lighthouse as the benchmark, the biggest wins came not from new optimization tricks but from removing what wasn't used. Simply looking at what is in the bundle with a bundle analyzer turns up several things to fix.

04Priority 3: fix CLS

  • Set width and height on images and videos so space is reserved.
  • Give late-loading areas such as ads and banners a minimum height.
  • Reduce web-font swap shifts with font-display and fallback font size adjustments.
  • Don't insert new elements above existing content. Pinning a cookie banner to the bottom of the screen is safe.

05Accessibility, best practices and SEO

The other three categories are mostly pass/fail checks, so fixing an item raises the score immediately.

CategoryCommon failuresFix
AccessibilityMissing image alt, low color contrast, unnamed buttons and linksAlt text, contrast of 4.5:1 or more, aria-label
Best practicesConsole errors, low-resolution images, outdated librariesFix errors, serve appropriately sized images
SEOMissing meta description, blocked crawling, link text like "click here"Write descriptions, check robots, descriptive link text

A Lighthouse SEO score of 100 doesn't guarantee search visibility; it only checks technical basics. That is why META_SCAN shows indexing, previews and AI signals cards alongside the Lighthouse scores.

06Why the score changes every run

Lighthouse is a lab measurement. Machine performance, network conditions and server response time make the same page score a few points differently on each run. Look at the trend across several runs rather than one number.

  • PageSpeed Insights and META_SCAN emulate a low-end mobile device on a slow network by default, so scores are lower than on your laptop's Chrome. That is expected.
  • Real-user experience comes from field data in the Chrome UX Report (CrUX). Search Console's Core Web Vitals report shows this data.
  • In the field, "good" means LCP within 2.5 s, INP within 200 ms and CLS under 0.1. INP can't be measured in the lab, so TBT serves as its proxy.

FAQ

Q. Is the Lighthouse score a ranking factor?
The Lighthouse score itself isn't. Google uses Core Web Vitals from real-user data as one of its page experience signals, and that weighs less than content relevance.
Q. Should I aim for 100?
No. A performance score of 90 or above is already in the "good" band, and beyond that the effort rarely changes what users feel. Fixing failing accessibility and SEO items usually pays off more.
Q. Desktop or mobile score?
Google indexes the mobile version first, so prioritize mobile. If mobile is good, desktop usually follows.

Related reading

  • SEO vs AEO vs GEO: What Each One Means
  • Heading Structure and Content Depth for SEO
  • Writing Title Tags and Meta Descriptions That Work

References

  • Chrome for Developers: Lighthouse performance scoring
  • web.dev: Web Vitals
  • web.dev: Optimize Largest Contentful Paint
  • web.dev: Optimize Cumulative Layout Shift
  • PageSpeed Insights

Author

Yuuuk94

Frontend developer who grew a product's MAU by 350% using SEO and Lighthouse as the yardstick, then turned that checklist into META_SCAN.

More about me →

How does your site do?

Enter one URL to run the free SEO/AEO/GEO checklist, including everything covered in this post.

Check for free