Lighthouse: PSI: "Browser errors were logged to console" due to Inspector-blocked resource

[Krinkle]

URL | Description
-- | --
/stats/matomo?idsite=… | Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector

What is the current behavior?

The "Best Practices" score is reduced to 92.

What is the expected behavior?

For resources blocked by PSI to not affect the score.

Environment Information

• Affected Channels: https://web.dev/measure/

[ndrozd]

having the same issue with google analytics

/g/collect?v=…(www.google-analytics.com) | Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector
-- | --

[Guzzox]

Any fix?

[patrickhulce]

@Krinkle @ndrozd @Guzzox any URL for us to be able to repro?

[Guzzox]

@patrickhulce My page doesn't have any Javascript in it check it out https://guzzox.xyz/

[patrickhulce]

Thanks @Guzzox! In your case it's not inspector blocked but net::ERR_ACCESS_DENIED on your CSS. That's strange the error appears to be logged even though the CSS loaded successfully.

@exterkamp does this help provide any clues at all?

[romainst]

Hi there,
I'm having the same issue with Facebook's Business pixel.
The request is apparently a POST which works but ends up in a 307 Internal redirect when running in a normal environment.

URL | Description
------------ | -------------
https://www.facebook.com/tr/ | Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector

Example site tested: http://www.france24.com/en/
Example report with the issue : https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fwww.france24.com%2Fen%2F#best-practices

[DemkivV]

I'm having the same issue with the Matomo plugin for WordPress.

Site: https://enso-web.design/
Report: https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fenso-web.design%2F
Issue:

URL | Description
-- | --
https://enso-web.design/wp-content/plugins/matomo/app/matomo.php | Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector

What's the best practice to solve this issue?

Edit
To me, there seem to be 3 possible solutions:

• Require analytic tool developers to build in a solid error handling
• Disable the adblocker (or whatever blocks these analytics tools) in the "online Lighthouse"
• Whitelist analytics tools, so they don't get blocked in the audit and thus negatively affect the rating.

I would expect similar results as in Lighthouse, used in Chrome locally. Despite using an adblocker, I didn't had issues as listed here. If the local Lighthouse in Chrome doesn't block resources, why should the online one from web.dev/measure/?

[Lofesa]

Same here whit analitycs in web.dev, not locally or in WPT

[spacedawwwg]

having the same issue with google analytics

/g/collect?v=…([www.google-analytics.com](http://www.google-analytics.com)) Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector

I came here hoping to find a solution to this. It seems to be when using Google's new analytics maybe?

[Lofesa]

What add-blocker can be turned off in PSI or web.dev ?

El lun., 23 nov. 2020 16:32, Osherz5 [e-mail] escribió:

Try turning off your ad blocker!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/lighthouse/issues/10198#issuecomment-732235195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFKOZCOZ6545SPIH3QHPNQ3SRJ6APANCNFSM4KEOJ4FA
.

[Lunnatica]

Hi,

Is there any update on this issue?

I've started seeing this error in some of my websites when using the new version of Google Analytics.

URL | Description
-- | --
/g/collect?v=…(www.google-analytics.com) | Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector

Example site: https://allthemeasurements.com/
Lighthouse report with the issue: https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fwww.allthemeasurements.com%2F

[crm911]

+1 for using the new Google Analytics:
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT.Inspector