Google Lighthouse is a free auditing tool built into Chrome DevTools that evaluates the performance, accessibility, best practices, and SEO of any web page in under a minute, assigning scores from 0 to 100 in each category.
If you've never audited your site with Lighthouse, there are almost certainly improvement opportunities you haven't spotted yet. This guide shows you how to run your first audit, interpret the results, and prioritize the changes that will have the most impact on your rankings and user experience.
How to Access Google Lighthouse
You have three ways to run Lighthouse, depending on your technical level and analysis environment:
1. Chrome DevTools (the fastest)
- Open Chrome and navigate to the URL you want to audit.
- Press
F12(or right-click → Inspect). - Go to the Lighthouse tab (it may be hidden behind the
>>button). - Select the categories to audit and the device type (Mobile or Desktop).
- Click Analyze page load.
Within 30–60 seconds you'll have a complete report right in the same tab.
2. PageSpeed Insights (for sharing results)
Visit pagespeed.web.dev, enter your URL, and click Analyze. PageSpeed Insights uses Lighthouse internally and adds real-world field data (CrUX) from actual Chrome users — something the DevTools version doesn't include.
3. Lighthouse CLI (for automation)
If you want to integrate audits into your CI/CD pipeline, install Lighthouse via npm: npm install -g lighthouse and run lighthouse https://yoursite.com --output html. Ideal for catching performance regressions before every deploy.
How to Interpret the Lighthouse Report
The report is divided into five categories, each scored from 0 to 100:
| Category | What it measures | Good score |
|---|---|---|
| Performance | Load speed (LCP, INP, CLS, TTFB) | ≥ 90 |
| Accessibility | Usability for people with disabilities | ≥ 90 |
| Best Practices | Security, HTTPS, console errors | ≥ 90 |
| SEO | Meta tags, robots.txt, mobile readability | ≥ 90 |
| PWA | Progressive Web App capabilities | Varies by goal |
The Performance category is the most complex and the most important for SEO. It's made up of several weighted metrics; the most relevant are the Core Web Vitals. You can explore them in depth in our web performance articles.
Performance Metrics Explained
- LCP (Largest Contentful Paint): time until the largest visual element is visible. Target: < 2.5 s.
- INP (Interaction to Next Paint): responsiveness to user interactions. Target: < 200 ms.
- CLS (Cumulative Layout Shift): visual stability — how much elements move while the page loads. Target: < 0.1.
- FCP (First Contentful Paint): time until the first visible content appears.
- Speed Index: how quickly the viewport fills up visually.
- TBT (Total Blocking Time): main thread blocking time, closely correlated with INP.
Opportunities and Diagnostics: Where the Gold Is
Below the score circles, Lighthouse shows three crucial sections:
Opportunities
These are improvements with an estimated time saving in seconds. Common examples:
- Eliminate render-blocking resources — CSS or JS in the
<head>withoutdeferorasync. - Properly size images — images in JPEG/PNG that should be served as WebP.
- Reduce server response time (TTFB) — may indicate hosting issues or missing cache.
- Remove unused JavaScript — code loaded but not executed on that specific page.
Diagnostics
These don't have a direct estimated time saving but point to architectural issues: missing width/height attributes on images, absence of cache policies, fonts without font-display: swap, and so on.
Passed Audits
The green list confirms what's already done right. Use it as a checklist to avoid breaking anything in future deploys.
Common Mistakes When Reading Lighthouse Results
- Auditing on Mobile and comparing with Desktop: mobile scores are significantly lower because Lighthouse simulates a slow 4G network and a limited CPU. These are different contexts — don't mix them.
- Running the audit with Chrome extensions active: ad blockers, password managers, and other extensions alter results. Always use an incognito window or a clean Chrome profile.
- Chasing a perfect 100: a Performance score of 90–95 already puts your page in the fastest segment of the web. The jump from 95 to 100 is often marginal in real-world impact.
- Ignoring field data (CrUX) in PageSpeed Insights: if there's a discrepancy between the lab report (Lighthouse) and field data, prioritize real data — it reflects your actual users' experience.
Key Takeaways
- Lighthouse runs from Chrome DevTools in seconds — no installation required.
- Use PageSpeed Insights to combine lab analysis with real user data (CrUX).
- Prioritize Opportunities with the largest estimated time savings; Diagnostics are second-pass improvements.
- Always audit in incognito mode with the target device type (mobile if most traffic is mobile).
- A Performance score ≥ 90 is already excellent — don't get paralyzed chasing 100.
- Review passed audits to make sure future changes don't break what's already working well.
If you need help implementing the improvements Lighthouse surfaces, the team at elenlace.com offers tailored web performance optimization services for small and medium businesses — reach out and we'll analyze your site with no commitment.
FAQ
Are Google Lighthouse and PageSpeed Insights the same thing?
Not exactly. PageSpeed Insights uses Lighthouse internally for lab analysis, but it also incorporates real-world field data from the Chrome User Experience Report (CrUX). Lighthouse in DevTools only provides simulated lab data. For SEO decisions, use PageSpeed Insights to see real user data alongside the lab results.
How often should I audit my site with Lighthouse?
At minimum, after every significant change: a new plugin, redesign, image updates, or hosting migration. If you run a high-traffic site or e-commerce store, integrate Lighthouse into your CI/CD pipeline to catch regressions automatically before every deploy.
Does a low Lighthouse score directly affect Google rankings?
Google uses Core Web Vitals (LCP, INP, CLS) as a ranking signal, not the Lighthouse numeric score directly. However, Lighthouse is the most practical tool for identifying and fixing the issues that affect those real metrics, so improving your Performance score generally improves your Core Web Vitals and, consequently, your rankings.
Why does my score vary between audits of the same page?
Lighthouse is sensitive to local machine load, network latency at that moment, and background OS processes. Variations of ±5–10 points between runs are normal. For more stable results, run the audit several times and look at the average range, or use webpagetest.org, which measures from servers under controlled conditions.
Prefer it done for you? El Enlace handles hosting and professional web development.
Further reading
Other providers and guides worth comparing:
