Provide the steps to reproduce

1. Run LH on any page. I used https://tolwin.spdns.org/index.html, but that is not important. You need access to the "access.log" of the webserver that is hosting the page under test.

What is the current behavior?

It is just a nit-picking, but probably worth mentioning. The Lighthouse report mentions the "UserAgent" in runtime settings. If you compare that user agent with the real user agent of the test requests, then they don't match.

I don't think this has any impact on the tests itself (at least not for me), but it is a little bit confusing to see requests with different user agents in your webserver's logfile coming from the same tool. Fixing this probably has no high prio, but maybe....if it is easy to fix....would be nice if this could be fixed/aligned.

I have attached two screenshots that hopefully illustrate the problem better. I was able to reproduce the issue on Lighthouse-Extension (3.0.2) and the build-in version of lighthouse in Chrome DevTools (3.0.0-beta.0), but this does NOT happen with the lighthouse test from webpagetest.org.

What is the expected behavior?

The user agent used by lighthouse should be consistent and match with the user agent mentioned in the runtime settings.

Environment Information

• Affected Channels: Lighthouse-Extension (3.0.2) and the build-in version of lighthouse in Chrome DevTools (3.0.0-beta.0)
• Lighthouse version:
• Node.js version:
• Operating System: CrOS Version 69.0.3473.0 (Offizieller Build) dev (64-Bit)
  
  

Related issues