LHS tracking for https://www.elkay.com/us/en.html - something not right

[Meet Kumar Jain]

Hello TEAM, 

If we check the LHS for the site - https://www.elkay.com/us/en.html

Its showing us a 100 score which seems not correct - https://pagespeed.web.dev/analysis/https-www-elkay-com-us-en-html/l24pmi1mdb?form_factor=mobile

We are seeing 403 in the Performance section & "View Treemap" . Something is not right. Please advise. 

When checked lighthouse via Google chrome extension - then its score is around 55. 

Regards, 

Meet

[❄ Johannes Henkel]

This mailinglist is about the crux report, not so much LightHouse. Plase treat my response regarding this with some grain of salt. :-)

I'd think that the webserver or cdn that responds to the request that PageSpeed insight's internal lighthouse is making responds with 403 (https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403), perhaps based on ip address or user agent or something similar.

Whereas, when you run lighthouse yourself, it responds differently - things work.

So I guess if you have control over this server, you could examine why / when it responds with 403 and unblock that, e.g. by looking at server logs and changing the config.

Either way - the lighthouse score you were able to record without the blockage would be more meaningful.

The field data in PagesPeed Insights (the upper part of the report you linked) is meaningful as well. It does not include the 403s - this is described in https://developer.chrome.com/docs/crux/methodology#page-eligibility: "If page is publicly discoverable for some users, but returns a non-success HTTP status in some circumstances, then those experiences won't be included in CrUX".

Good wishes.

--
You received this message because you are subscribed to the Google Groups "Chrome UX Report (Discussions)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-ux-repo...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ux-report/0915af4a-c84c-4c4f-a8f4-4af44eaa1a1bn%40chromium.org.