If not, open Chrome's main menu andĪccess it at the top of the menu. In Chrome, go to the page you want to audit.īe next to the Chrome address bar. Sites and authenticated pages, while the extension does not.Ĭhrome Extension from the Chrome Webstore. The DevTools workflow allows for testing local Rather than this Chrome Extension workflow. Run Lighthouse as a Chrome Extension Note: Unless you have a specific reason, you should use the Chrome DevTools workflow See Using programmatically for an example of running Lighthouse The -g flag installs it as a global module. Install and run the Node command line tool After 30 to 60 seconds, Lighthouse gives you a reportįigure 2. DevTools shows you a list of audit categories.Ĭlick Run audit.
To the right is the Audits panel of Chrome DevTools, whichĬlick Perform an audit. To the left is the viewport of the page that will beĪudited. You can audit any URL on the web.įigure 1. In Google Chrome, go to the URL you want to audit.Lighthouse powers the Audits panel of Chrome DevTools. Note: The CLI and Node workflows require you to have an instance of Google Chrome Run Lighthouse and link to reports without Integrate Lighthouse into your continuous Automate your Lighthouse runs via shell scripts. Easily audit pages that require authentication,Īnd read your reports in a user-friendly format. Choose the Lighthouse workflow that suits you best:
0 kommentar(er)
