Hello, I have a question about the --extra-headers parameter.
I tried to use lighthouse https://huixie.iflyrec.com/list --extra-headers "{\"sessionkey\":\"32a86fbaac004c048b0ab674875c1657\",\"websessionkey \":\"c063d532ca5a4d50a0a97f5e944339bd\"}"
I used it to test the performance of my product, but the cookie information was not set successfully, is there something wrong with the way I wrote it?
Can you help me see what my problem is? A million thanks.
What did you expect?
Please help me find my problem.
What have you tried?
I also tried to use, read the local json file, but also did not succeed, the json content is: {"Cookie": "sessionkey=6032da97e3c44fcb89ab9ca7effe1003&domain=huixie.iflyrec.com; websessionkey= 77d975e1e89047d2bfafb75c316a181a&domain=.iflyrec.com"}
How were you running Lighthouse?
CLI
Lighthouse Version
12.1.0
Chrome Version
126.0.6478.115
Node Version
v20.15.0
OS
Windows 11
Relevant log output
LH:ChromeLauncher Waiting for browser. +0ms
LH:ChromeLauncher Waiting for browser... +2ms
LH:ChromeLauncher Waiting for browser..... +510ms
LH:ChromeLauncher Waiting for browser.....√ +2ms
LH:status Connecting to browser +648ms
LH:status Navigating to about:blank +12ms
LH:status Benchmarking machine +20ms
LH:status Preparing target for navigation mode +1s
LH:status Cleaning origin data +17ms
LH:status Cleaning browser cache +31ms
LH:status Preparing network conditions +22ms
LH:status Navigating to https://huixie.iflyrec.com/list +112ms
LH:status Getting artifact: DevtoolsLog +34s
LH:status Getting artifact: Trace +0ms
LH:status Getting artifact: RootCauses +1ms
LH:status Getting artifact: Accessibility +823ms
LH:status Getting artifact: AnchorElements +1s
LH:status Getting artifact: ConsoleMessages +120ms
LH:status Getting artifact: CSSUsage +0ms
LH:status Getting artifact: Doctype +320ms
LH:status Getting artifact: DOMStats +3ms
LH:status Getting artifact: FontSize +38ms
LH:status Getting artifact: Inputs +595ms
LH:status Getting artifact: ImageElements +12ms
LH:method <= browser ERR:error Runtime.evaluate +2s
LH:method <= browser ERR:error Runtime.evaluate +280ms
LH:method <= browser ERR:error Runtime.evaluate +245ms
LH:method <= browser ERR:error Runtime.evaluate +262ms
LH:method <= browser ERR:error Runtime.evaluate +270ms
LH:status Getting artifact: InspectorIssues +154ms
LH:status Getting artifact: JsUsage +1ms
LH:status Getting artifact: LinkElements +0ms
LH:status Getting artifact: MainDocumentContent +6ms
LH:status Getting artifact: MetaElements +1ms
LH:status Getting artifact: NetworkUserAgent +4ms
LH:status Getting artifact: OptimizedImages +1ms
LH:status Getting artifact: ResponseCompression +4s
LH:status Getting artifact: RobotsTxt +11ms
LH:status Getting artifact: Scripts +160ms
LH:status Getting artifact: SourceMaps +1ms
LH:status Getting artifact: Stacks +0ms
LH:status Collect stacks +1ms
LH:status Getting artifact: Stylesheets +30ms
LH:status Getting artifact: TraceElements +0ms
LH:status Getting artifact: ViewportDimensions +25ms
LH:status Getting artifact: devtoolsLogs +3ms
LH:status Getting artifact: traces +0ms
LH:status Getting artifact: FullPageScreenshot +1ms
LH:status Getting artifact: BFCacheFailures +1s
LH:status Analyzing and running audits... +816ms
LH:status Auditing: Uses HTTPS +5ms
LH:status Auditing: Redirects HTTP traffic to HTTPS +21ms
LH:status Auditing: Has a `<meta name="viewport">` tag with `width` or `initial-scale` +6ms
LH:status Auditing: First Contentful Paint +7ms
LH:status Auditing: Largest Contentful Paint +84ms
LH:status Auditing: First Meaningful Paint +18ms
LH:status Auditing: Speed Index +2ms
LH:status Auditing: Screenshot Thumbnails +498ms
LH:status Auditing: Final Screenshot +2ms
LH:status Auditing: Total Blocking Time +7ms
LH:status Auditing: Max Potential First Input Delay +22ms
LH:status Auditing: Cumulative Layout Shift +16ms
LH:status Auditing: No browser errors logged to the console +5ms
LH:status Auditing: Initial server response time was short +9ms
LH:status Auditing: Time to Interactive +8ms
LH:status Auditing: User Timing marks and measures +15ms
LH:status Auditing: Avoid chaining critical requests +12ms
LH:status Auditing: Avoid multiple page redirects +13ms
LH:status Auditing: Displays images with correct aspect ratio +11ms
LH:status Auditing: Serves images with appropriate resolution +11ms
LH:status Auditing: Avoids deprecated APIs +8ms
LH:status Auditing: Avoids third-party cookies +6ms
LH:status Auditing: Minimizes main-thread work +3ms
LH:status Auditing: JavaScript execution time +89ms
LH:status Auditing: Preconnect to required origins +67ms
LH:status Auditing: All text remains visible during webfont loads +5ms
LH:status Auditing: Diagnostics +5ms
LH:status Auditing: Network Requests +2ms
LH:status Auditing: Network Round Trip Times +18ms
LH:status Auditing: Server Backend Latencies +5ms
LH:status Auditing: Tasks +18ms
LH:status Auditing: Metrics +20ms
LH:status Auditing: Resources Summary +26ms
LH:status Auditing: Minimize third-party usage +5ms
LH:status Auditing: Lazy load third-party resources with facades +30ms
LH:status Auditing: Largest Contentful Paint element +22ms
LH:status Auditing: Largest Contentful Paint image was not lazily loaded +10ms
LH:status Auditing: Avoid large layout shifts +2ms
LH:status Auditing: Avoid long main-thread tasks +18ms
LH:status Auditing: Avoid non-composited animations +12ms
LH:status Auditing: Image elements have explicit `width` and `height` +2ms
LH:status Auditing: Page has valid source maps +3ms
LH:status Auditing: Preload Largest Contentful Paint image +11ms
LH:status Auditing: Ensure CSP is effective against XSS attacks +12ms
LH:status Auditing: Script Treemap Data +9ms
LH:status Auditing: `[accesskey]` values are unique +48ms
LH:status Auditing: `[aria-*]` attributes match their roles +131ms
LH:status Auditing: Uses ARIA roles only on compatible elements +5ms
LH:status Auditing: `button`, `link`, and `menuitem` elements have accessible names +8ms
LH:status Auditing: ARIA attributes are used as specified for the element's role +2ms
LH:status Auditing: Deprecated ARIA roles were not used +2ms
LH:status Auditing: Elements with `role="dialog"` or `role="alertdialog"` have accessible names. +6ms
LH:status Auditing: `[aria-hidden="true"]` is not present on the document `<body>` +1ms
LH:status Auditing: `[aria-hidden="true"]` elements do not contain focusable descendents +8ms
LH:status Auditing: ARIA input fields have accessible names +2ms
LH:status Auditing: ARIA `meter` elements have accessible names +2ms
LH:status Auditing: ARIA `progressbar` elements have accessible names +6ms
LH:status Auditing: Elements use only permitted ARIA attributes +3ms
LH:status Auditing: `[role]`s have all required `[aria-*]` attributes +4ms
LH:status Auditing: Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. +10ms
LH:status Auditing: `[role]`s are contained by their required parent element +11ms
LH:status Auditing: `[role]` values are valid +3ms
LH:status Auditing: Elements with the `role=text` attribute do not have focusable descendents. +3ms
LH:status Auditing: ARIA toggle fields have accessible names +7ms
LH:status Auditing: ARIA `tooltip` elements have accessible names +56ms
LH:status Auditing: ARIA `treeitem` elements have accessible names +8ms
LH:status Auditing: `[aria-*]` attributes have valid values +6ms
LH:status Auditing: `[aria-*]` attributes are valid and not misspelled +10ms
LH:status Auditing: Buttons have an accessible name +10ms
LH:status Auditing: The page contains a heading, skip link, or landmark region +8ms
LH:status Auditing: Background and foreground colors have a sufficient contrast ratio +17ms
LH:status Auditing: `<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements. +12ms
LH:status Auditing: Definition list items are wrapped in `<dl>` elements +13ms
LH:status Auditing: Document has a `<title>` element +24ms
LH:status Auditing: ARIA IDs are unique +17ms
LH:status Auditing: All heading elements contain content. +4ms
LH:status Auditing: No form fields have multiple labels +5ms
LH:status Auditing: `<frame>` or `<iframe>` elements have a title +3ms
LH:status Auditing: Heading elements appear in a sequentially-descending order +4ms
LH:status Auditing: `<html>` element has a `[lang]` attribute +4ms
LH:status Auditing: `<html>` element has a valid value for its `[lang]` attribute +10ms
LH:status Auditing: `<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute. +7ms
LH:status Auditing: Identical links have the same purpose. +3ms
LH:status Auditing: Image elements have `[alt]` attributes +4ms
LH:status Auditing: Image elements do not have `[alt]` attributes that are redundant text. +8ms
LH:status Auditing: Input buttons have discernible text. +5ms
LH:status Auditing: `<input type="image">` elements have `[alt]` text +2ms
LH:status Auditing: Elements with visible text labels have matching accessible names. +3ms
LH:status Auditing: Form elements have associated labels +3ms
LH:status Auditing: Document has a main landmark. +15ms
LH:status Auditing: Links have a discernible name +20ms
LH:status Auditing: Links are distinguishable without relying on color. +7ms
LH:status Auditing: Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). +34ms
LH:status Auditing: List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements +24ms
LH:status Auditing: The document does not use `<meta http-equiv="refresh">` +11ms
LH:status Auditing: `[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5. +3ms
LH:status Auditing: `<object>` elements have alternate text +12ms
LH:status Auditing: Select elements have associated label elements. +16ms
LH:status Auditing: Skip links are focusable. +22ms
LH:status Auditing: No element has a `[tabindex]` value greater than 0 +4ms
LH:status Auditing: Tables have different content in the summary attribute and `<caption>`. +13ms
LH:status Auditing: Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption. +13ms
LH:status Auditing: Touch targets have sufficient size and spacing. +6ms
LH:status Auditing: `<td>` elements in a large `<table>` have one or more table headers. +8ms
LH:status Auditing: Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table. +12ms
LH:status Auditing: `<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe. +4ms
LH:status Auditing: `[lang]` attributes have a valid value +5ms
LH:status Auditing: `<video>` elements contain a `<track>` element with `[kind="captions"]` +5ms
LH:status Auditing: Custom controls have associated labels +3ms
LH:status Auditing: Custom controls have ARIA roles +0ms
LH:status Auditing: User focus is not accidentally trapped in a region +1ms
LH:status Auditing: Interactive controls are keyboard focusable +2ms
LH:status Auditing: Interactive elements indicate their purpose and state +2ms
LH:status Auditing: The page has a logical tab order +13ms
LH:status Auditing: The user's focus is directed to new content added to the page +0ms
LH:status Auditing: Offscreen content is hidden from assistive technology +2ms
LH:status Auditing: HTML5 landmark elements are used to improve navigation +1ms
LH:status Auditing: Visual order on the page follows DOM order +1ms
LH:status Auditing: Uses efficient cache policy on static assets +2ms
LH:status Auditing: Avoids enormous network payloads +6ms
LH:status Auditing: Defer offscreen images +9ms
LH:status Auditing: Eliminate render-blocking resources +17ms
LH:status Auditing: Minify CSS +47ms
LH:status Auditing: Minify JavaScript +77ms
LH:status Auditing: Reduce unused CSS +205ms
LH:status Auditing: Reduce unused JavaScript +6ms
LH:status Auditing: Serve images in next-gen formats +11ms
LH:status Auditing: Efficiently encode images +8ms
LH:status Auditing: Enable text compression +112ms
LH:status Auditing: Properly size images +8ms
LH:status Auditing: Use video formats for animated content +8ms
LH:status Auditing: Remove duplicate modules in JavaScript bundles +4ms
LH:status Auditing: Avoid serving legacy JavaScript to modern browsers +7ms
LH:status Auditing: Page has the HTML doctype +123ms
LH:status Auditing: Properly defines charset +2ms
LH:status Auditing: Avoids an excessive DOM size +4ms
LH:status Auditing: Avoids requesting the geolocation permission on page load +5ms
LH:status Auditing: No issues in the `Issues` panel in Chrome Devtools +3ms
LH:status Auditing: Avoids `document.write()` +5ms
LH:status Auditing: Detected JavaScript libraries +3ms
LH:status Auditing: Avoids requesting the notification permission on page load +2ms
LH:status Auditing: Allows users to paste into input fields +2ms
LH:status Auditing: Use HTTP/2 +1ms
LH:status Auditing: Uses passive listeners to improve scrolling performance +7ms
LH:status Auditing: Document has a meta description +2ms
LH:status Auditing: Page has successful HTTP status code +4ms
LH:status Auditing: Document uses legible font sizes +3ms
LH:status Auditing: Links have descriptive text +3ms
LH:status Auditing: Links are crawlable +2ms
LH:status Auditing: Page isn’t blocked from indexing +2ms
LH:status Auditing: robots.txt is valid +3ms
LH:status Auditing: Document has a valid `hreflang` +6ms
LH:status Auditing: Document has a valid `rel=canonical` +2ms
LH:status Auditing: Structured data is valid +2ms
LH:status Auditing: Page didn't prevent back/forward cache restoration +1ms
LH:status Generating results... +3ms
LH:Printer html output written to C:\Users\leixu10\Desktop\lighthouse\huixie.iflyrec.com_2024-06-27_14-58-01.report.html +58ms
LH:CLI Protip: Run lighthouse with `--view` to immediately open the HTML report in your browser +3ms
LH:ChromeLauncher Killing Chrome instance 14636 +1ms
FAQ
URL
https://huixie.iflyrec.com/list
What happened?
Hello, I have a question about the --extra-headers parameter. I tried to use lighthouse https://huixie.iflyrec.com/list --extra-headers "{\"sessionkey\":\"32a86fbaac004c048b0ab674875c1657\",\"websessionkey \":\"c063d532ca5a4d50a0a97f5e944339bd\"}" I used it to test the performance of my product, but the cookie information was not set successfully, is there something wrong with the way I wrote it?
Can you help me see what my problem is? A million thanks.
What did you expect?
Please help me find my problem.
What have you tried?
I also tried to use, read the local json file, but also did not succeed, the json content is: {"Cookie": "sessionkey=6032da97e3c44fcb89ab9ca7effe1003&domain=huixie.iflyrec.com; websessionkey= 77d975e1e89047d2bfafb75c316a181a&domain=.iflyrec.com"}
How were you running Lighthouse?
CLI
Lighthouse Version
12.1.0
Chrome Version
126.0.6478.115
Node Version
v20.15.0
OS
Windows 11
Relevant log output