Lighthouse

Automated auditing, performance metrics, and best practices for the web.

Performance
GoogleChrome/lighthousedeveloper.chrome.com/docs/lighthouse/overview/lighthouse

README

Lighthouse  GitHub Actions Status Badge GitHub Actions Status Badge GitHub Actions Status Badge Coverage Status Build tracker for Lighthouse NPM lighthouse package


Lighthouse analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices.


- Using Lighthouse
  - Using Lighthouse in Chrome DevTools
  - Using the Chrome extension
  - Using the Node CLI
    CLI options
  - Using the Node module
  - Viewing a report
    Online Viewer
  - Docs & Recipes
  - Developing Lighthouse
    Setup
    Run
    Tests
    Docs
- Associated Products and Projects
  - Lighthouse Integrations in Web Perf services
  - Lighthouse Integrations in non-Web Perf services
  - Plugins
  - Related projects
- FAQ
  How does Lighthouse work?
  Can I configure the lighthouse run?
  How does Lighthouse use network throttling, and how can I make it better?
  Are results sent to a remote server?
  How do I get localized Lighthouse results?
  How do I author custom audits to extend Lighthouse?
  How do I contribute?

Using Lighthouse in Chrome DevTools


Lighthouse is integrated directly into the Chrome DevTools, under the "Lighthouse" panel.

Installation: install Chrome.

Run it: open Chrome DevTools, select the Lighthouse panel, and hit "Generate report".

Lighthouse integration in Chrome DevTools.

Using the Chrome extension


The Chrome extension was available prior to Lighthouse being available in Chrome Developer Tools, and offers similar functionality.

Installation: install the extension from the Chrome Web Store.

Run it: follow the extension quick-start guide.

Using the Node CLI


The Node CLI provides the most flexibility in how Lighthouse runs can be configured and reported. Users who want more advanced usage, or want to run Lighthouse in an automated fashion should use the Node CLI.

_Lighthouse requires Node 16 LTS (16.x) or later._

Installation:

  1. ```sh
  2. npm install -g lighthouse
  3. # or use yarn:
  4. # yarn global add lighthouse
  5. ```

Run it: lighthouse https://airhorner.com/

By default, Lighthouse writes the report to an HTML file. You can control the output format by passing flags.

CLI options


<!-- To update the help output:
  node cli --help | pbcopy
-->

  1. ```
  2. $ lighthouse --help

  4. lighthouse <url> <options>

  6. Logging:
  7.   --verbose  Displays verbose logging  [boolean] [default: false]
  8.   --quiet    Displays no progress, debug logs, or errors  [boolean] [default: false]

  10. Configuration:
  11.   --save-assets                  Save the trace contents & devtools logs to disk  [boolean] [default: false]
  12.   --list-all-audits              Prints a list of all available audits and exits  [boolean] [default: false]
  13.   --list-trace-categories        Prints a list of all required trace categories and exits  [boolean] [default: false]
  14.   --print-config                 Print the normalized config for the given config and options, then exit.  [boolean] [default: false]
  15.   --additional-trace-categories  Additional categories to capture with the trace (comma-delimited).  [string]
  16.   --config-path                  The path to the config JSON.
  17.                                  An example config file: core/config/lr-desktop-config.js  [string]
  18.   --preset                       Use a built-in configuration.
  19.                                  WARNING: If the --config-path flag is provided, this preset will be ignored.  [string] [choices: "perf", "experimental", "desktop"]
  20.   --chrome-flags                 Custom flags to pass to Chrome (space-delimited). For a full list of flags, see https://bit.ly/chrome-flags
  21.                                  Additionally, use the CHROME_PATH environment variable to use a specific Chrome binary. Requires Chromium version 66.0 or later. If omitted, any detected Chrome Canary or Chrome stable will be used.  [string] [default: ""]
  22.   --port                         The port to use for the debugging protocol. Use 0 for a random port  [number] [default: 0]
  23.   --hostname                     The hostname to use for the debugging protocol.  [string] [default: "localhost"]
  24.   --form-factor                  Determines how performance metrics are scored and if mobile-only audits are skipped. For desktop, --preset=desktop instead.  [string] [choices: "mobile", "desktop"]
  25.   --screenEmulation              Sets screen emulation parameters. See also --preset. Use --screenEmulation.disabled to disable. Otherwise set these 4 parameters individually: --screenEmulation.mobile --screenEmulation.width=360 --screenEmulation.height=640 --screenEmulation.deviceScaleFactor=2
  26.   --emulatedUserAgent            Sets useragent emulation  [string]
  27.   --max-wait-for-load            The timeout (in milliseconds) to wait before the page is considered done loading and the run should continue. WARNING: Very high values can lead to large traces and instability  [number]
  28.   --enable-error-reporting       Enables error reporting, overriding any saved preference. --no-enable-error-reporting will do the opposite. More: https://github.com/GoogleChrome/lighthouse/blob/main/docs/error-reporting.md  [boolean]
  29.   --gather-mode, -G              Collect artifacts from a connected browser and save to disk. (Artifacts folder path may optionally be provided). If audit-mode is not also enabled, the run will quit early.
  30.   --audit-mode, -A               Process saved artifacts from disk. (Artifacts folder path may be provided, otherwise defaults to ./latest-run/)
  31.   --only-audits                  Only run the specified audits  [array]
  32.   --only-categories              Only run the specified categories. Available categories: accessibility, best-practices, performance, pwa, seo  [array]
  33.   --skip-audits                  Run everything except these audits  [array]
  34.   --budget-path                  The path to the budget.json file for LightWallet.  [string]

  36. Output:
  37.   --output       Reporter for the results, supports multiple values. choices: "json", "html", "csv"  [array] [default: ["html"]]
  38.   --output-path  The file path to output the results. Use 'stdout' to write to stdout.
  39.                    If using JSON output, default is stdout.
  40.                    If using HTML or CSV output, default is a file in the working directory with a name based on the test URL and date.
  41.                    If using multiple outputs, --output-path is appended with the standard extension for each output type. "reports/my-run" -> "reports/my-run.report.html", "reports/my-run.report.json", etc.
  42.                    Example: --output-path=./lighthouse-results.html  [string]
  43.   --view         Open HTML report in your browser  [boolean] [default: false]

  45. Options:
  46.   --version                            Show version number  [boolean]
  47.   --help                               Show help  [boolean]
  48.   --cli-flags-path                     The path to a JSON file that contains the desired CLI flags to apply. Flags specified at the command line will still override the file-based ones.
  49.   --locale                             The locale/language the report should be formatted in
  50.   --blocked-url-patterns               Block any network requests to the specified URL patterns  [array]
  51.   --disable-storage-reset              Disable clearing the browser cache and other storage APIs before a run  [boolean]
  52.   --throttling-method                  Controls throttling method  [string] [choices: "devtools", "provided", "simulate"]
  53.   --throttling
  54.   --throttling.rttMs                   Controls simulated network RTT (TCP layer)
  55.   --throttling.throughputKbps          Controls simulated network download throughput
  56.   --throttling.requestLatencyMs        Controls emulated network RTT (HTTP layer)
  57.   --throttling.downloadThroughputKbps  Controls emulated network download throughput
  58.   --throttling.uploadThroughputKbps    Controls emulated network upload throughput
  59.   --throttling.cpuSlowdownMultiplier   Controls simulated + emulated CPU throttling
  60.   --extra-headers                      Set extra HTTP Headers to pass with request
  61.   --precomputed-lantern-data-path      Path to the file where lantern simulation data should be read from, overwriting the lantern observed estimates for RTT and server latency.  [string]
  62.   --lantern-data-output-path           Path to the file where lantern simulation data should be written to, can be used in a future run with the `precomputed-lantern-data-path` flag.  [string]
  63.   --plugins                            Run the specified plugins  [array]
  64.   --channel  [string] [default: "cli"]
  65.   --chrome-ignore-default-flags  [boolean] [default: false]

  67. Examples:
  68.   lighthouse <url> --view                                                                          Opens the HTML report in a browser after the run completes
  69.   lighthouse <url> --config-path=./myconfig.js                                                     Runs Lighthouse with your own configuration: custom audits, report generation, etc.
  70.   lighthouse <url> --output=json --output-path=./report.json --save-assets                         Save trace, screenshots, and named JSON report.
  71.   lighthouse <url> --screenEmulation.disabled --throttling-method=provided --no-emulatedUserAgent  Disable device emulation and all throttling
  72.   lighthouse <url> --chrome-flags="--window-size=412,660"                                          Launch Chrome with a specific window size
  73.   lighthouse <url> --quiet --chrome-flags="--headless"                                             Launch Headless Chrome, turn off logging
  74.   lighthouse <url> --extra-headers "{\"Cookie\":\"monster=blue\", \"x-men\":\"wolverine\"}"        Stringify'd JSON HTTP Header key/value pairs to send in requests
  75.   lighthouse <url> --extra-headers=./path/to/file.json                                             Path to JSON file of HTTP Header key/value pairs to send in requests
  76.   lighthouse <url> --only-categories=performance,pwa                                               Only run the specified categories. Available categories: accessibility, best-practices, performance, pwa, seo

  78. For more information on Lighthouse, see https://developers.google.com/web/tools/lighthouse/.
  79. ```

Output Examples

  1. ```sh
  2. lighthouse
  3. # saves `./<HOST>_<DATE>.report.html`

  5. lighthouse --output json
  6. # json output sent to stdout

  8. lighthouse --output html --output-path ./report.html
  9. # saves `./report.html`

  11. # NOTE: specifying an output path with multiple formats ignores your specified extension for *ALL* formats
  12. lighthouse --output json --output html --output-path ./myfile.json
  13. # saves `./myfile.report.json` and `./myfile.report.html`

  15. lighthouse --output json --output html
  16. # saves `./_.report.json` and `./<HOST>_<DATE>.report.html`

  18. lighthouse --output-path=~/mydir/foo.out --save-assets
  19. # saves `~/mydir/foo.report.html`
  20. # saves `~/mydir/foo-0.trace.json` and `~/mydir/foo-0.devtoolslog.json`

  22. lighthouse --output-path=./report.json --output json
  23. # saves `./report.json`
  24. ```

Lifecycle Examples
You can run a subset of Lighthouse's lifecycle if desired via the --gather-mode (-G) and  --audit-mode (-A) CLI flags.

  1. ```sh
  2. lighthouse http://example.com -G
  3. # launches browser, collects artifacts, saves them to disk (in `./latest-run/`) and quits

  5. lighthouse http://example.com -A
  6. # skips browser interaction, loads artifacts from disk (in `./latest-run/`), runs audits on them, generates report

  8. lighthouse http://example.com -GA
  9. # Normal gather + audit run, but also saves collected artifacts to disk for subsequent -A runs.


  12. # You can optionally provide a custom folder destination to -G/-A/-GA. Without a value, the default will be `$PWD/latest-run`.
  13. lighthouse -GA=./gmailartifacts https://gmail.com
  14. ```


Notes on Error Reporting


The first time you run the CLI you will be prompted with a message asking you if Lighthouse can anonymously report runtime exceptions. The Lighthouse team uses this information to detect new bugs and avoid regressions. Opting out will not affect your ability to use Lighthouse in any way. Learn more.

Using the Node module

You can also use Lighthouse programmatically with the Node module.

Read Using Lighthouse programmatically for help getting started.\
Read Lighthouse Configuration to learn more about the configuration options available.

Viewing a report


Lighthouse can produce a report as JSON or HTML.

HTML report:

Lighthouse example audit

Online Viewer


Running Lighthouse with the --output=json flag generates a JSON dump of the run.
You can view this report online by visiting
and dragging the file onto the app. You can also use the "Export" button from the
top of any Lighthouse HTML report and open the report in the
Lighthouse Viewer.

In the Viewer, reports can be shared by clicking the share icon in the top
right corner and signing in to GitHub.

Note: shared reports are stashed as a secret Gist in GitHub, under your account.


Docs & Recipes


Useful documentation, examples, and recipes to get you started.

Docs

- Dealing with variance
- Using Lighthouse programmatically
- Testing a site with authentication
- Developing Plugins
- Making a New Audit
- Testing on a mobile device
- Setting a performance budget
- Lighthouse Architecture

Recipes

- Plugin - example Lighthouse plugin
- Custom Audit example - extend Lighthouse, run your own audits

Videos

The session from Google I/O 2018 covers the new performance engine, upcoming Lighthouse REST API, and using the Chrome UX report to evaluate real-user data.
Watch the Lighthouse @ Google I/O 2018 session.

The session from Google I/O 2017 covers architecture, writing custom audits,
GitHub/Travis/CI integration, headless Chrome, and more:
Watch the Lighthouse @ Google I/O 2017 session.

_Click the image to watch the video on YouTube._

Develop


Read on for the basics of hacking on Lighthouse. Also, see Contributing
for detailed information.

Setup


  1. ```sh
  2. # yarn should be installed first

  4. git clone https://github.com/GoogleChrome/lighthouse

  6. cd lighthouse
  7. yarn
  8. yarn build-all
  9. ```

Run


  1. ```sh
  2. node cli http://example.com
  3. # append --chrome-flags="--no-sandbox --headless --disable-gpu" if you run into problems connecting to Chrome
  4. ```

Getting started tip: node --inspect-brk cli http://example.com to open up Chrome DevTools and step

through the entire app. See [Debugging Node.js with Chrome
DevTools](https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27#.59rma3ukm)
for more info.

Tests


  1. ```sh
  2. # lint and test all files
  3. yarn test

  5. # watch for file changes and run tests
  6. #   Requires http://entrproject.org : brew install entr
  7. yarn watch

  9. ## run linting, unit, and smoke tests separately
  10. yarn lint
  11. yarn unit
  12. yarn smoke

  14. ## run tsc compiler
  15. yarn type-check
  16. ```

Docs


Some of our docs have tests that run only in CI by default. To modify our documentation, you'll need to run yarn build-pack && yarn test-docs locally to make sure they pass.

Additional Dependencies
- brew install jq

Lighthouse Integrations in Web Perf services


This section details services that have integrated Lighthouse data. If you're working on a cool project integrating Lighthouse and would like to be featured here, file an issue to this repo or tweet at us @_____lighthouse!

Web Page Test — An open source tool for measuring and analyzing the performance of web pages on real devices. Users can choose to produce a Lighthouse report alongside the analysis of WebPageTest results.

HTTPArchive - HTTPArchive tracks how the web is built by crawling 500k pages with Web Page Test, including Lighthouse results, and stores the information in BigQuery where it is publicly available.

Calibre - Calibre is a comprehensive performance monitoring platform running on Lighthouse. See the performance impact of your work before it hits production with GitHub Pull Request Reviews. Track the impact of Third Party scripts. Automate your performance system with a developer-first Node.js API. Try Calibre with a free 15-day trial.

DebugBear - DebugBear is a website monitoring tool based on Lighthouse. See how your scores and metrics changed over time, with a focus on understanding what caused each change. DebugBear is a paid product with a free 30-day trial.

Treo - Treo is Lighthouse as a Service. It provides regression testing, geographical regions, custom networks, and integrations with GitHub & Slack. Treo is a paid product with plans for solo-developers and teams.

Alertdesk - Alertdesk is based on Lighthouse and helps you to keep track of your site’s quality & performance. Run daily quality & performance tests from both Mobile and Desktop and dive into the powerful & intuitive reports. You can also monitor your uptime (every minute - 24/7) & domain health. Alertdesk is a paid product with a free 14-day trial.

Screpy - Screpy is a web analysis tool that can analyze all pages of your websites in one dashboard and monitor them with your team. It's powered by Lighthouse and it also includes some different analysis tools (SERP, W3C, Uptime, etc). Screpy has free and paid plans.

Lighthouse Keeper - Lighthouse Keeper monitors your pages' Lighthouse scores and notifies you if they drop below your thresholds. Lighthouse Keeper is a free service that monitors up to 3 URLs once per day.

Siteimprove Performance — Siteimprove Performance is a web Performance monitoring solution that enables a marketer, manager or decision maker to understand and optimize website load times. Get easy-to-use insights with a focus on quick and impactful wins. Siteimprove Performance is a paid product with a free 14-day trial.

SpeedCurve — SpeedCurve is a tool for continuously monitoring web performance across different browsers, devices, and regions. It can aggregate any metric including Lighthouse scores across multiple pages and sites, and allows you to set performance budgets with Slack or email alerts. SpeedCurve is a paid product with a free 30-day trial.

Speedrank - Speedrank monitors the performance of your website in the background. It displays Lighthouse reports over time and delivers recommendations for improvement. Speedrank is a paid product with 14-day-trial.

Foo - Lighthouse-as-a-service offering free and premium plans. Provides monitoring and historical reporting of Lighthouse audits with CircleCI, GitHub, and other integrations. Features include Slack notifications, PR comment reporting and more.

Apdex - Apdex is a website performance service. The main features are historical Lighthouse report visualizations, mobile/desktop options, alerts, uptime monitoring, and more. There are flexible paid plans and a 30-day free trial.

Websu - Websu is an open source project to provide Lighthouse-as-a-Service through a simple HTTP REST API. The main features are ability to host and deploy in your own environment and historical Lighthouse report summaries.

DTEKT.IO - DTEKT is a website performance and uptime monitoring service. It uses lighthouse to provide visibility into the performance of websites from multiple locations on multiple devices. It offers three months free trial and paid plans.

SpeedVitals - SpeedVitals is a Lighthouse powered tool to measure web performance across multiple devices and locations. It has various features like Layout Shift Visualization, Waterfall Chart, Field Data and Resource Graphs. SpeedVitals offers both free and paid plans.

Lighthouse Metrics - Lighthouse Metrics gives you global performance insights with a single test. You can also monitor your websites on a daily or hourly base. Lighthouse Metrics offers free global one-time tests and performance monitoring as a paid feature with a free 14-day trial.

Auditzy - Auditzy™ is a robust website auditing & monitoring tool which lets you analyze your web page(s) pre-user journey. Analyze the Competitor Health Metric, Core Web Vitals, and Technology. Compare your web pages with your competitors to understand where you are leading or lagging. Real-time notification with Slack. Have Seamless Collaboration with Multiple Teams. Automate your Audits hourly, daily, weekly, and so on. It has a free trial with pay as you go plans.

Lighthouse Integrations in non-Web Perf services


PageWatch — PageWatch is a tool to find problem pages on your website.  It provides insights into spelling errors, layout issues, slow pages (powered by Lighthouse) and more.  PageWatch is offered via free and paid plans.

SEO Guard — SEO Guard is a website monitoring solution. It provides metrics based on Lighthouse scores. The service is offered via free and paid premium plans.

Fluxguard - Fluxguard provides website DOM change monitoring orchestrated with Google Puppeteer, and audited by Lighthouse. Fluxguard is a freemium product, with monthly monitoring of up to 75 pages for free.

Microlink — Microlink is a cloud browser as API. It offers Lighthouse reports on demand, making it easy to build any service on top. Similar functionality is available via the underlying open-source project named browserless.

Peyk - Peyk is a website change detection & monitoring service. Peyk can detect changes in cookies, network requests, technologies, local & session storage, lighthouse audits, screenshots and so much more. Peyk is offered via free and paid plans.

Wattspeed — Wattspeed is a free tool that generates snapshots - historical captures of your web pages that include Lighthouse scores, a list of technologies, W3C HTML validator results, DOM size, mixed content info, and more.

AwesomeTechStack — AwesomeTechStack is a free to use website tech stack analyzer. AwesomeTechStack provides insights into the security, modernity, and performance of any website's technology stack and guidance to improve performance. Lighthouse insights are a crucial part of a website's tech stack rating.

Plugins


lighthouse-plugin-field-performance - a plugin that adds real-user performance metrics for the URL using the data from Chrome UX Report.

lighthouse-plugin-publisher-ads - a tool to improve ad speed and overall quality through a series of automated audits. At the moment, this is primarily targeted at sites using Google Ad Manager. This tool will aid in resolving discovered problems, providing a tool to be used to evaluate effectiveness of iterative changes while suggesting actionable feedback.

lighthouse-plugin-crux - a plugin that quickly gathers real-user-metrics data from the Chrome UX Report API.

Related projects


Other awesome open source projects that use Lighthouse.

auto-lighthouse - a CLI for crawling a domain and generating mobile and desktop reports for each page.
Exthouse - Analyze the impact of a browser extension on web performance.
Garie - An open source tool for monitoring performance using Lighthouse,  PageSpeed Insights, Prometheus, Grafana and Docker.
Gimbal - An open source (MIT licensed) tool used to measure, analyze, and budget aspects of a web application. Gimbal also integrates reports with GitHub pull requests.
Gradle Lighthouse Plugin - An open source Gradle plugin that runs Lighthouse tests on multiple URLs and asserts category score thresholds (useful in continuous integration).
lightcrawler - Crawl a website and run each page found through Lighthouse.
lighthouse-badges - Generate gh-badges (shields.io) based on Lighthouse performance.
lighthouse-batch - Run Lighthouse over a number of sites and generate a summary of their metrics/scores.
lighthouse-batch-parallel - Run multiple Lighthouse runs in parallel to accelerate the data collecting process, get the result stream (csv, json, js object) in your own process (warning: performance results may be volatile).
lighthouse-check-action - A GitHub Action to run Lighthouse in a workflow, featuring Slack notifications and report upload to S3.
lighthouse-check-orb - A CircleCI Orb to run Lighthouse in a workflow, featuring Slack notifications and report upload to S3.
andreasonny83/lighthouse-ci - Run Lighthouse and assert scores satisfy your custom thresholds.
GoogleChrome/lighthouse-ci - (official) Automate running Lighthouse for every commit, viewing the changes, and preventing regressions.
lighthouse-ci-action - A GitHub Action that makes it easy to run Lighthouse in CI and keep your pages small using performance budgets.
lighthouse-cron - Cron multiple batch Lighthouse audits and emit results for sending to remote server.
lighthouse-gh-reporter - Run Lighthouse in CI and report back in a comment on your pull requests
lighthouse-hue - Set the color of Philips Hue lights based on a Lighthouse score
lighthouse-jest-example - Gather performance metrics via Lighthouse and assert results with Jest; uses Puppeteer to start Chrome with network emulation settings defined by WebPageTest.
lighthouse-lambda - Run Lighthouse on AWS Lambda with prebuilt stable desktop Headless Chrome.
lighthouse-magic-light - Set the color of the MagicLight Bluetooth Smart Light Bulb based on Lighthouse score
lighthouse-mocha-example - Run Lighthouse performance tests with Mocha and chrome-launcher.
lighthouse-monitor - Run Lighthouse against all your URLs. Send metrics to any backend you want, save all reports with automatic data retention, and compare any two results in a web UI.
lighthouse-persist - Run Lighthouse and upload HTML reports to an AWS S3 bucket.
lighthouse-viewer - Render the Lighthouse JSON into a report, using the Lighthouse Report Renderer repackaged as UMD and ESM. Also available with React, Svelte and Vue wrappers.
lighthouse4u - LH4U provides Google Lighthouse as a service, surfaced by both a friendly UI+API, and backed by Elastic Search for easy querying and visualization.
performance-budgets - Easily assert Lighthouse budgets with Docker.
pwmetrics - Gather performance metrics
react-lighthouse-viewer - Render a Lighthouse JSON report in a React Component.
site-audit-seo - CLI tool for SEO site audit, crawl site, lighthouse each page. Output to console and tables in csv, xlsx, json, web or Google Drive.
webpack-lighthouse-plugin - Run Lighthouse from a Webpack build.
is-website-vulnerable - An open source Node.js CLI tool that finds publicly known security vulnerabilities in a website's frontend JavaScript libraries.
cypress-audit - Run Lighthouse and Pa11y audits directly in your E2E test suites.

FAQ


How does Lighthouse work?


See Lighthouse Architecture.

Why is the performance score so low? It looks fine to me.


Lighthouse reports the performance metrics as they would be experienced by a typical mobile user on a 4G connection and a mid-tier ~$200 phone. Even if it loads quickly on your device and network, users in other environments will experience the site very differently.

Read more in our guide to throttling.

Why does the performance score change so much?


Lighthouse performance scores will change due to inherent variability in web and network technologies, even if there hasn't been a code change. Test in consistent environments, run Lighthouse multiple times, and beware of variability before drawing conclusions about a performance-impacting change.

Read more in our guide to reducing variability.

Can I configure the lighthouse run?


Yes! Details in Lighthouse configuration.

How does Lighthouse use network throttling, and how can I make it better?


Good question. Network and CPU throttling are applied by default in a Lighthouse run. The network
attempts to emulate slow 4G connectivity and the CPU is slowed down 4x from your machine's default speed. If you
prefer to run Lighthouse without throttling, you'll have to use the CLI and disable it with the
--throttling.* flags mentioned above.

Read more in our guide to network throttling.

Are results sent to a remote server?


Nope. Lighthouse runs locally, auditing a page using a local version of the Chrome browser installed on the
machine. Report results are never processed or beaconed to a remote server.

How do I get localized Lighthouse results via the CLI?


Starting in Lighthouse 8.0, Lighthouse relies entirely on native Intl support and no longer uses an Intl polyfill. If you're using Node 14 or later, there should be no issue because Node is now [built with full-icu by default](https://nodejs.medium.com/node-js-12-to-lts-and-node-js-13-is-here-e28d6a4a2bd#9514).

However, if you're using a small-icu Node build, you may see Lighthouse log messages about your locale not being available. To remedy this, you can manually install ICU data by using the [full-icu](https://www.npmjs.com/package/full-icu) module and the [--icu-data-dir node flag](https://nodejs.org/api/intl.html#intl_providing_icu_data_at_runtime) at launch.

How do I author custom audits to extend Lighthouse?


Tip: see Lighthouse Architecture for more information

on terminology and architecture.

Lighthouse can be extended to run custom audits and gatherers that you author.
This is great if you're already tracking performance metrics in your site and
want to surface those metrics within a Lighthouse report.

If you're interested in running your own custom audits, check out our
Custom Audit Example over in recipes.

How do I contribute?


We'd love help writing audits, fixing bugs, and making the tool more useful!
See Contributing to get started.

Lighthouse logo
Lighthouse, ˈlītˌhous (n): a tower or other structure tool containing a beacon light to warn or guide ships at sea developers.