Running Lighthouse audit through CLI is not giving correct metrics and as I see on view map, login page is captured and metrics is collected but metrics should have captured from different page(specific)

[prashanthramanna]

FAQ

• Yes, my issue is not about variability or throttling.
• Yes, my issue is not about a specific accessibility audit (file with axe-core instead).

URL

https://qatirehubonline.com

What happened?

I tried running Lighthouse based on the steps mentioned here in the link - https://github.com/GoogleChrome/lighthouse/blob/main/docs/authenticated-pages.md

The set up is done as mentioned in the above link with the all the supporting softwares
installed node js v18.18, Lighthouse 11.0, chrome 119

1. open command prompt and navigate to folder where chrome-debug file is located
2. Run chrome-debug. This logs the debugging port of your Chrome instance.
3. Navigating to web application and log in.
4. In a separate terminal, I am run lighthouse with command using the port number from chrome-debug.
   and the command is

lighthouse --screenEmulation.disabled --throttling-method=provided --emulatedUserAgent--form-factor desktop --only-categories=performance --port <Port#>--view

even though the session is logged in and above command uses the same session, still could see the page screen shot captured in view map of the report is showing the login page instead of specific page for which I need the results
also observed that the actual URL is getting replaced with denied URL at the top of the report

I am bit confused as the page screenshot and the URL seems to be irrelevant for me on seeing the lighthouse report

What did you expect?

on running the Lighthouse audit through CLI should run and generate the report for different pages of my web application

What have you tried?

tried the steps that I have mentioned above

tried to generate the lighthouse report by using the above command through CLI for this page
https:///customerconnect/account/
but URL captured in the report is something like this
https:///b2b/portal/login/access/denied/ which seems to be redirected to login page

Observed LH:CriConnection:warn Cannot create new tab; reusing open tab. and
LH:Navigation:error Provided URL did not match initial navigation URL +16s on the CLI but that should not cause any error to run the lighthouse audit I hope

Not sure why the redirection is happening

How were you running Lighthouse?

CLI

Lighthouse Version

V 11.0

Chrome Version

119

Node Version

18.18

OS

Windows

Relevant log output

No response

[prashanthramanna]

Can any one please let me know which this redirection issue occurring on running Lighthouse through CLI

[adamraine]

Can you please verify your Lighthouse version, the console log and screenshot you provided look like they were taken from Lighthouse v9.x or earlier.

You may also want to use the flag --disable-storage-reset as the documentation you linked indicates.