Outdated browser used.

[StonehengeCreations]

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).
• Yes, my issue is not answered by other FAQs.

URL

https://www.gidspatrick.nl

What happened?

The built-in LightHouse in Chrome's Developer Tools uses an outdated browser versions:
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36
and
Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Mobile Safari/537.36

What did you expect?

Chrome 119 dates back to November 14, 2023, while the current version is 136.

As Chrome auto-updates itself, no real user is using such an outdated version - only (bad) bots do.
Many websites, like mine, block legacy browsers for security reasons resulting in 403 errors.

LightHouse should simply use the actual browser version. Why simulate a different version that the user is not even using? Now, while testing I am forced to lower / drop security rules, because of this unneeded simulation.

What have you tried?

Temporarily deleted legacy browser checks in the .htaccess file, making the website(s) vulnerable during testing.

How were you running Lighthouse?

Chrome DevTools

Lighthouse Version

12.5.1

Chrome Version

136.0.0.0

Node Version

No response

OS

macOS 15.4.1

Relevant log output

[tagliala]

Additional information:

Chrome 119 is currently incompatible with modern Rails applications that use the modern browser targeting feature, as defined by the new allow_browser option rails/rails#50505. This allows Rails apps to specify minimum browser versions for "modern" clients.

Reference: rails/rails@dc34e29

This issue tracked in rails/rails#53486 resurfaced again