GoogleChrome / lighthouse

Automated auditing, performance metrics, and best practices for the web.
https://developer.chrome.com/docs/lighthouse/overview/
Apache License 2.0
28.32k stars 9.36k forks source link

Lighthouse says to defer webside logo (which is visible) #9496

Closed johanlantz closed 5 years ago

johanlantz commented 5 years ago

Provide the steps to reproduce

  1. Run LH on https://givensa.com

What is the current behavior?

Lightouse says to defer the website logo "/img/givensa-logo....jpg"

What is the expected behavior?

The logo is always visible and it is always the first image to load on the page, it seems weird that Lighthouse wants to defer it (it will always be above the fold on page load).

Environment Information

Latest Lighthouse version through chrome.

Related issues

patrickhulce commented 5 years ago

Thanks for filing! I'm not seeing this in version 5.2.0 of Lighthouse which is Chrome Canary, just the facebook.png which is indeed not immediately visible. image

johanlantz commented 5 years ago

Hi Patrick, Thanks for the quick answer, much appreciated.

Indeed with Canary I get better results (nice UX update btw).

Just fyi, from a 3 min test on Canary I see some potential inconsistencies.

patrickhulce commented 5 years ago

Hm, I'm not seeing the same results for the image deferred as you. It is flagging a product image on that page, but its one that is only shown after you click the thumbnail of it, so that's indeed an offscreen image. The URLs differ by just a single character, is it possible there was some confusion there?

Regarding the copyright text, the latest version of axe does not flag that copyright text as a contrast issue (we use axe-core under the hood). If you believe this is a bug, I'm sure they'd appreciate a bug in their repo :) (we would automatically pick up any fix the next time we update)

johanlantz commented 5 years ago

Thanks Patrick, No worries about copyrights, just noticed there was a difference between LH versions.

As for the last image flagged as deferable, this no longer happens on Canary, I have retested various times and it is all good now. No idea why but issue is no longer there in Canary.

Ok to close, many thanks for the support and have a nice weekend.