PageSpeed creates console errors on WebSocket requests

GoogleChrome / lighthouse

Automated auditing, performance metrics, and best practices for the web.

https://developer.chrome.com/docs/lighthouse/overview/

Apache License 2.0

28.38k stars 9.37k forks source link

PageSpeed creates console errors on WebSocket requests #12459

Open ealmiladi opened 3 years ago

ealmiladi commented 3 years ago

Provide the steps to reproduce

Run LH on https://artisanresume.com

What is the current behavior?

What is the expected behavior?

Either Lighthouse should permit these network requests, or ignore the browser errors related to them as they're not representative of the client experience.

Environment Information

Affected Channels: Web.dev

patrickhulce commented 3 years ago

Thanks for filing @ealmiladi! They're not being blocked (that would be indicated by net::ERR_BLOCKED_BY_CLIENT) but they do appear to consistently timeout only in web.dev/LR (example). Backend folks will need to take a look at what's going on here 👍

ealmiladi commented 3 years ago

Thanks Patrick!

PaulRudin commented 3 years ago

Similarly I have web app that opens a websocket connection to a Google Cloud Run hosted backend (with a .run.app dns name). It works fine in the browser, but from the console log that lighthouse complains about, apparently there's a dns resolution failure.

Edit: to be clear - it works fine e.g. from lighthouse in devtools - it's just the web.dev hosted version that's problematic.

adamraine commented 2 months ago

The originally report page doesn't reproduce this anymore but this page does: https://youimmi.com/. The root cause does appear to be web socket requests.

rsmything commented 2 months ago

@adamraine what's the way to fix this issue related with name error on https://youimmi.com. It works fine in dev console in lighthouse, but it reproduces on pagespeed insights. Due to this issue we aren't able to reach 100/100 points