 Barry Pollard [X](https://twitter.com/tunetheweb) [GitHub](https://github.com/tunetheweb) [Mastodon](https://mastodon.social/@tunetheweb) [Bluesky](https://bsky.app/profile/tunetheweb.com) [Homepage](https://www.tunetheweb.com)  Connor Clark [X](https://twitter.com/cjamcl) [GitHub](https://github.com/connorjclark)
Published: Oct 10, 2025
[Lighthouse is a website auditing tool](https://developer.chrome.com/docs/lighthouse/overview.md.txt) that helps developers with metrics, insights and diagnostics to improve the user experience of their sites.
Lighthouse 13 is available immediately on the [command line through npm](https://www.npmjs.com/package/lighthouse), in [Chrome Canary](https://www.google.com/chrome/canary/), and will be available in [PageSpeed Insights](https://pagespeed.web.dev/) within the next week. It will land in Chrome stable in Chrome 143.
See the full list of changes in the [13.0 changelog](https://github.com/GoogleChrome/lighthouse/releases/tag/v13.0.0).
## Removal of various performance audits which have been replaced by newer insights
As [announced previously](https://developer.chrome.com/blog/moving-lighthouse-to-insights.md.txt) we have consolidated our **Lighthouse performance audits** and DevTools **Performance panel** insights into common performance insights available in both tools.
In Lighthouse 12 we switched the default view in Lighthouse reports to display these insights and in Lighthouse 13 we are removing the old audits from both the report and the underlying JSON.
We are thankful to the community for [the feedback](https://github.com/GoogleChrome/lighthouse/discussions/16462) that helped improve the Insights allowing for a smoother change over.
> [!IMPORTANT]
> **Important:** There are no changes to the [performance scoring](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring.md.txt) in this version of Lighthouse, which is based on the metrics rather than the audits. Only the non-scored audits are changing.
The following audits have been replaced from Lighthouse 13 onwards and the replaced audits are no longer available as of this version:
| New insight audit id | Replacing audit id(s) |
|---|---|
| `cls-culprits-insight` | `layout-shifts` |
| `document-latency-insight` | `redirects` `server-response-time` `uses-text-compression` |
| `dom-size-insight` | `dom-size` |
| `duplicated-javascript-insight` | `duplicated-javascript` |
| `font-display-insight` | `font-display` |
| `image-delivery-insight` | `modern-image-formats` `uses-optimized-images` `efficient-animated-content` `uses-responsive-images` |
| `interaction-to-next-paint-insight` | `work-during-interaction` |
| `lcp-discovery-insight` | `prioritize-lcp-image` `lcp-lazy-loaded` |
| `lcp-phases-insight` | `largest-contentful-paint-element` |
| `legacy-javascript-insight` | `legacy-javascript` |
| `modern-http-insight` | `uses-http2` |
| `network-dependency-tree-insight` | `critical-request-chains` `uses-rel-preconnect` |
| `render-blocking-insight` | `render-blocking-resources` |
| `third-parties-insight` | `third-party-summary` |
| `use-cache-insight` | `uses-long-cache-ttl` |
| `viewport-insight` | `viewport` |
Renamed and consolidated audits
> [!NOTE]
> **Note:** There some small differences to [the previously announced consolidations](https://developer.chrome.com/blog/moving-lighthouse-to-insights.md.txt#renamed_and_consolidated_audits) with `non-composited-animations` and `unsized-images` still remaining as a separate diagnostic audit to help identify those that don't cause CLS issues as well.
## Removed audits
In addition to the aforementioned replacements, the following audits have been removed with no replacements as it was felt these no longer served useful purposes:
| **Removed audits** | **Reason for removal** |
|---|---|
| `first-meaningful-paint` | Older metric that is no longer recommended (replaced by LCP). |
| `font-size` | While small fonts is a legibility issue, there are no signals that this remains an SEO concern today. Additionally, this audit was very expensive to run and maintain. |
| `no-document-write` | Rarely an issue in first-party scripts these days, and it is inactionable for third-party scripts that use this. |
| `offscreen-images` | Offscreen images are already deprioritized by the browser so while lazy loading helps reduce bandwidth, it is unlikely to have an impact on what Lighthouse measures. |
| `preload-fonts` | Not enabled due to risks of over recommending. |
| `third-party-facades` | This audit covers limited facades and some developers expressed concern using non-affiliated third-party facades. Ultimately, we would prefer the third-parties improve their offerings rather than work around them. |
| `uses-passive-event-listeners` | Rarely an issue in first-party scripts these days, and it is inactionable for third-party scripts that use this. |
| `uses-rel-preload` | Not enabled due to risks of over recommending. |
Removed audits
> [!NOTE]
> **Note:** There some small differences to [the previously announced removals](https://developer.chrome.com/blog/moving-lighthouse-to-insights.md.txt#removed_audits) with `preload-fonts` and `font-size` also now being removed.
## Documentation for the new insights audits
We have [documented the new audits](https://developer.chrome.com/docs/performance/insights) and linked from the new Lighthouse reports. The old documentation will be kept around for the foreseeable future so prior versions of Lighthouse can still link to them.
## Other changes
Lighthouse 13 requires Node 22.19 or higher.
## Running Lighthouse
Lighthouse is available in [Chrome DevTools](https://developer.chrome.com/docs/devtools/overview.md.txt), [npm](https://www.npmjs.com/package/lighthouse) (as a Node module and a CLI tool), and as a browser extension (in [Chrome](https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk) and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/google-lighthouse/)). It also powers several Google services, including [PageSpeed Insights](https://pagespeed.web.dev/).
To try the Lighthouse Node CLI, use the following commands:
```text
npm install -g lighthouse
lighthouse https://www.example.com --view
```
## Get in touch with the Lighthouse team
To discuss the new features, changes in the Lighthouse 13 release, or anything else related to Lighthouse:
- Report an issue or submit feedback in the [Lighthouse GitHub issue tracker](https://github.com/GoogleChrome/lighthouse/issues).
- Ask questions in the [Lighthouse GitHub discussion forums](https://github.com/GoogleChrome/lighthouse/discussions).