![]() ![]() "reports/my-run" -> "reports/", "reports/", etc.Įxample: -output-path=./lighthouse-results.html If using multiple outputs, -output-path is appended with the standard extension for each output type. If using HTML or CSV output, default is a file in the working directory with a name based on the test URL and date. output-path The file path to output the results. output Reporter for the results, supports multiple values. disable-full-page-screenshot Disables collection of the full page screenshot, which can be quite large budget-path The path to the budget.json file for LightWallet. skip-audits Run everything except these audits Available categories: accessibility, best-practices, performance, pwa, seo only-categories Only run the specified categories. only-audits Only run the specified audits (Artifacts folder path may be provided, otherwise defaults to. audit-mode, -A Process saved artifacts from disk. If audit-mode is not also enabled, the run will quit early. (Artifacts folder path may optionally be provided). gather-mode, -G Collect artifacts from a connected browser and save to disk. ![]() no-enable-error-reporting will do the opposite. enable-error-reporting Enables error reporting, overriding any saved preference. WARNING: Very high values can lead to large traces and instability max-wait-for-load The timeout (in milliseconds) to wait before the page is considered done loading and the run should continue. emulatedUserAgent Sets useragent emulation Otherwise set these 4 parameters individually: -screenEmulation.mobile -screenEmulation.width=360 -screenEmulation.height=640 viceScaleFactor=2 Use -screenEmulation.disabled to disable. screenEmulation Sets screen emulation parameters. form-factor Determines how performance metrics are scored and if mobile-only audits are skipped. hostname The hostname to use for the debugging protocol. port The port to use for the debugging protocol. If omitted, any detected Chrome Canary or Chrome stable will be used. For a full list of flags, see Īdditionally, use the CHROME_PATH environment variable to use a specific Chrome binary. chrome-flags Custom flags to pass to Chrome (space-delimited). WARNING: If the -config-path flag is provided, this preset will be ignored. config-path The path to the config JSON.Īn example config file: core/config/lr-desktop-config.js additional-trace-categories Additional categories to capture with the trace (comma-delimited). list-trace-categories Prints a list of all required trace categories and exits list-all-audits Prints a list of all available audits and exits save-assets Save the trace contents & devtools logs to disk quiet Displays no progress, debug logs, or errors Lighthouse requires Node 18 LTS (18.x) or later. Users who want more advanced usage, or want to run Lighthouse in an automated fashion should use the Node CLI. ![]() The Node CLI provides the most flexibility in how Lighthouse runs can be configured and reported. ![]() Run it: follow the extension quick-start guide. Installation: install the extension from the Chrome Web Store. The Chrome extension was available prior to Lighthouse being available in Chrome Developer Tools, and offers similar functionality. Run it: open Chrome DevTools, select the Lighthouse panel, and hit "Generate report". Lighthouse is integrated directly into the Chrome DevTools, under the "Lighthouse" panel. How do I author custom audits to extend Lighthouse?.How do I get localized Lighthouse results?.How does Lighthouse use network throttling, and how can I make it better?.Lighthouse Integrations in non-Web Perf services.Lighthouse Integrations in Web Perf services.Lighthouse analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |