Web.dev - Lighthouse blocks network requests to Firebase, incorrectly flagging browser errors

[ealmiladi]

Provide the steps to reproduce

1. 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]

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]

Thanks Patrick!

[PaulRudin]

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.