![Brendan Kenny](https://web.dev/images/authors/brendankenny.jpg) Brendan Kenny [GitHub](https://github.com/brendankenny) [Bluesky](https://bsky.app/profile/brendankenny.bsky.social) Eric Bidelman [X](https://twitter.com/ebidel) [GitHub](https://github.com/ebidel) [Homepage](http://ericbidelman.com/)
[Lighthouse](https://developer.chrome.com/docs/lighthouse/overview) is an [open-source](https://github.com/GoogleChrome/lighthouse), automated tool for improving the quality of your web apps. You can install it as a [Chrome Extension](https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk) or run it as a Node command line tool. When you give Lighthouse a URL, it runs a barrage of tests against the page and then generates a report explaining how well the page did and indicating areas for improvement. ![Lighthouse Logo](https://developer.chrome.com/static/blog/lighthouse-jan/image/lighthouse-logo-98f4dda3526a6.png) Lighthouse Logo Today, we're happy to announce the [1.5 release](https://github.com/GoogleChrome/lighthouse/releases/tag/1.5.0) of Lighthouse, a huge release, with over **128 PRs** . Lighthouse 1.5 includes a bunch of big new features, audits, and the usual bug fixes. You can install it from npm (`npm i -g lighthouse`) or [download the extension](https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk) from the Chrome Web Store. ## New Audits The **CSS Usage Audit** reports the number of unused style rules in your page and the cost/time savings of removing them: ![CSS Usage Audit](https://developer.chrome.com/static/blog/lighthouse-jan/image/css-usage-audit-eb5197478c0f.png) The **Optimized Images Audit** reports images that are unoptimized and the cost/time savings of optimizing them: ![Optimized Images AudiT](https://developer.chrome.com/static/blog/lighthouse-jan/image/optimized-images-audit-aaf984b0865d3.png) The **Responsive Images Audit** reports images that are too big and the potential cost/time savings of sizing them correctly for the given device: ![Optimized Images AudiT](https://developer.chrome.com/static/blog/lighthouse-jan/image/optimized-images-audit-12a3e284d8b8a.png) The **Deprecations and Interventions Audit** lists console warnings from Chrome if your page is using deprecated APIs or features that have [interventions](https://www.chromestatus.com/features#intervention): ![Deprecations and Interventions Audit](https://developer.chrome.com/static/blog/lighthouse-jan/image/deprecations-interventio-da24227a23992.png) ## Report changes As you've seen, we've focused on making the report less visually cluttered by adding tabular data, hiding extraneous help text, and adding new features to make it easier to navigate the data. ### Emulation settings It's easy to forget what throttling and emulation settings were used for a particular Lighthouse run. Lighthouse reports now include the **runtime emulation settings** that were used to create the report; a [long time feature request](https://github.com/GoogleChrome/lighthouse/issues/568): ![Emulation settings](https://developer.chrome.com/static/blog/lighthouse-jan/image/emulation-settings-1821f12db2d22.gif) ### More useful trace data Lighthouse metrics like "First meaningful paint", "Time to Interactive", etc are mocked out as User Timing measures and injected back into the trace data saved with the `--save-assets` flag. If you use the `--save-assets` flag, you can now drop the trace into DevTools or open it in the [DevTools Timeline Viewer](https://chromedevtools.github.io/timeline-viewer/). You'll be able to see your key metrics in context with the full trace of the page load. ![Trace data](https://developer.chrome.com/static/blog/lighthouse-jan/image/trace-data-72d92bc0bf45c.png) ## Lighthouse Viewer In HTML reports, you'll notice a new button with options for exporting the report in different formats. One of those options is "Open in Viewer". Clicking this button will send the report to the online [Viewer](https://googlechrome.github.io/lighthouse/viewer/), where you can further share the report with GitHub users. ![Open in Viewer button](https://developer.chrome.com/static/blog/lighthouse-jan/image/open-viewer-button-27638d734fed4.png) ![Open in Viewer result](https://developer.chrome.com/static/blog/lighthouse-jan/image/open-viewer-result-5f088cb2c3a87.png) Behind the scenes, Viewer gets your permission via OAuth to create a GitHub [secret gist](https://help.github.com/articles/about-gists/#secret-gists) and saves the report there. Since it's done as your Gist, you maintain full control over the sharing of the report and you can delete it at any time. You can revoke the Viewer's permission to create gists under your [GitHub settings](https://github.com/settings/applications). ## Performance Experiment The first version of the [Performance Experiment](https://github.com/GoogleChrome/lighthouse/issues/1143) project has landed in 1.5.0. This lets you experiment with your page load performance, interactively testing the effects of blocking or delaying assets in your critical path **during development**. When Lighthouse is run with the `--interactive` flag, a special report is generated that allows interactive selection of costly page resources. The experiment server then reruns Lighthouse on that page with those resources blocked. ![Toggling runtime settings](https://developer.chrome.com/static/blog/lighthouse-jan/image/toggling-runtime-settings-86a54ec655806.png) [Learn more](https://docs.google.com/document/d/1FYt5Es_Kf5IyC_bkTHj2G_a_sTvRvIq5iZCEN8VZY5o/edit#heading=h.cetla8h0y4o) about the Performance Experiment in Lighthouse. ## New Documentation Last but not least, we've modernized the documentation at [developers.google.com/web/tools/lighthouse/](https://developers.google.com/web/tools/lighthouse/) and added new audit references. ![New documentation](https://developer.chrome.com/static/blog/lighthouse-jan/image/new-documentation-7954e5de20ca7.png) That's it for now! For all the details on the latest in Lighthouse, see the [full release notes](https://github.com/GoogleChrome/lighthouse/releases/tag/1.5.0) over on GitHub. As always, [hit us up](https://github.com/GoogleChrome/lighthouse/graphs/contributors) to [report bugs](https://github.com/GoogleChrome/lighthouse/issues), file feature requests, or brainstorm [ideas](https://github.com/GoogleChrome/lighthouse/issues?q=is:issue+is:open+label:%22good+first+bug%22) on what you'd like to see next.