Lighthouse Score Optimizer
Enter your current Lighthouse scores, set targets, and get a prioritized fix list with estimated score impact per fix. No data leaves your browser.
Your Current Scores (0 – 100)
Score Overview & Gap Analysis
Score Budget — Points to Gain per Fix
Prioritized Fix List
Sorted by estimated score impact. Fixes marked HIGH give the most points per unit of effort.
How Lighthouse Scores Are Calculated
Google Lighthouse audits your page in a simulated environment — a mobile device with throttled CPU and a 4G-equivalent network connection — and measures six timing metrics. Each metric value is converted to a 0–100 score using a log-normal distribution calibrated against millions of real-world pages. The metric scores are then combined using a weighted average: Largest Contentful Paint (25%), Total Blocking Time (30%), Cumulative Layout Shift (25%), First Contentful Paint (10%), and Speed Index (10%). The result is your Performance score.
Accessibility, Best Practices, and SEO scores work differently — they are pass/fail audits where each audit is weighted by severity. Failing a high-weight audit (like missing image alt text) has a large impact; failing a low-weight audit (like a missing meta description) has a smaller impact. This means a few targeted fixes can dramatically improve these scores, while Performance improvements require actually making the page faster.
The Highest-Impact Performance Fixes
1. Eliminate Render-Blocking Resources
Any CSS or JavaScript loaded in the <head> without async or defer blocks the browser from rendering the page. Lighthouse penalizes render-blocking resources through their contribution to First Contentful Paint and Total Blocking Time. The fix is to inline critical CSS directly in the <head> (styles needed for above-the-fold content), load the rest asynchronously, and add defer to all non-critical scripts. This single fix can recover 10–20 Performance points on script-heavy pages.
2. Optimize the Largest Contentful Paint Element
LCP accounts for 25% of the Performance score. The LCP element is almost always a hero image or a large heading. For images: serve in WebP or AVIF format, add fetchpriority="high" to the LCP image, preload it with <link rel="preload" as="image">, and ensure it is not lazy-loaded. Reducing the LCP image from 500KB to 80KB (WebP) on a 4G connection saves about 0.8 seconds, which can push a borderline Needs-Improvement score firmly into Good.
3. Reduce Total Blocking Time
TBT measures how long the main thread is blocked — unable to respond to user input — during page load. The primary cause is large JavaScript bundles. Every script that takes more than 50ms to execute contributes to TBT. Solutions include code-splitting with dynamic import(), moving heavy computations to a Web Worker, removing unused third-party scripts (tag managers, chat widgets, analytics pixels), and deferring analytics to load after the main content is interactive.
Quick Wins for Accessibility
Accessibility scores are often the most improvable in a single sprint because the failures tend to be discrete, fixable issues rather than architectural problems. The five most common Lighthouse Accessibility failures are: missing alt attributes on <img> elements, insufficient color contrast, missing form labels, incorrect ARIA roles or missing ARIA names on interactive elements, and a broken heading hierarchy (jumping from h1 to h4). Fixing these five categories typically takes 2–4 hours and reliably moves scores from 70 into the 90s.
Color contrast is worth special attention because it is the most frequently failed audit and the one most developers overlook. Text must achieve a contrast ratio of at least 4.5:1 against its background for normal-weight text, and 3:1 for large text (18px+ bold or 24px+ regular). Light gray text on white backgrounds — a popular design choice — almost always fails. Use a contrast checker to audit your color palette before implementing.
Best Practices and SEO Fixes
The Best Practices score covers security and modern web standards. Common failure points are: serving resources over HTTP instead of HTTPS (critical, high weight), using deprecated APIs like document.write() or XMLHttpRequest synchronously, missing a Content-Security-Policy header, and displaying images at incorrect aspect ratios. Most Best Practices issues can be resolved at the server configuration level without touching application code.
The SEO score audits technical SEO signals that Lighthouse can detect locally. Required elements include: a <meta name="description"> tag, a valid <title> tag (10–60 characters), a <meta name="viewport"> tag, an HTTP 200 status code, crawlable links (href attributes, not JavaScript-driven navigation), and robots.txt and hreflang tags where relevant. An SEO score of 90+ does not guarantee search rankings, but it confirms your page's technical foundation is sound.
Setting Realistic Score Targets
For most production sites, achieving 90+ across all four categories is a realistic target with concentrated effort. However, some site types have structural score ceilings. Heavy e-commerce pages with many product images, live price fetches, and third-party payment widgets will struggle to reach 90 Performance — aim for 70–80 and focus on field data (Core Web Vitals) rather than lab scores. Single-page applications often have lower Performance scores due to JavaScript execution overhead, but high Accessibility and SEO scores are always achievable regardless of framework.
Prioritize fixes by the gap between your current score and 90 in each category, weighted by category importance. Performance matters most for SEO (Core Web Vitals are a ranking factor). Accessibility matters for legal compliance and user experience. SEO and Best Practices are largely pass/fail checklists that can be cleared in a single engineering sprint.
Frequently Asked Questions
What is a good Lighthouse score?
Google Lighthouse scores range from 0 to 100. Scores of 90-100 are considered Good (green), 50-89 Need Improvement (orange), and 0-49 are Poor (red). For SEO impact, aim for all four categories above 90. Performance scores below 50 can directly affect Core Web Vitals rankings.
Which Lighthouse fixes have the highest impact on the Performance score?
The highest-impact Performance fixes are: eliminating render-blocking resources (can recover 10-20 points), properly sizing images and serving next-gen formats like WebP/AVIF (5-15 points), removing unused JavaScript and CSS (5-10 points), enabling text compression (3-8 points), and improving server response time / TTFB (2-10 points).
How does Lighthouse calculate the Performance score?
The Lighthouse Performance score is a weighted average of six metrics: First Contentful Paint (10%), Largest Contentful Paint (25%), Total Blocking Time (30%), Cumulative Layout Shift (25%), Speed Index (10%). Each raw metric value is converted to a 0-100 score using a log-normal distribution, then the weights are applied. TBT and LCP together account for 55% of the score.
Why does my Lighthouse score vary between runs?
Lighthouse scores vary due to network conditions, CPU throttling simulation variance, and background processes. To get a stable reading: run in incognito mode, close other tabs, run 3-5 times and use the median score. Differences of 5-10 points between runs on the same page are normal.
What is the fastest way to improve a low Accessibility score?
The quickest Accessibility wins are: adding alt text to images, ensuring sufficient color contrast ratios (4.5:1 for normal text), adding labels to all form inputs, fixing heading hierarchy, and ensuring all interactive elements are keyboard-focusable. These five fixes resolve the majority of common failures and can push a score from 70 to 95+.