Google Lighthouse V8 – Improved CLS metrics • Hacker News Board

Re: Google Lighthouse V8 – Improved CLS metrics

#51

Post by hoten » Thu, Jun 03, 2021, 4:28 PM UTC

tills13 wrote: post #46

Is CLS still broken for single page apps?

Can you elaborate? If you are referring to the long duration of a SPA, we resolved that by making CLS windowed: https://web.dev/evolving-cls/

Re: Google Lighthouse V8 – Improved CLS metrics

#52

Post by hoten » Thu, Jun 03, 2021, 4:31 PM UTC

hobbescotch wrote: post #38

disasterkitsltd wrote: post #36

Earlier quoted context omitted.

Ironically I've found the CLI to be the only stable channel of Lighthouse. What do you see that docker fixes?

Fixes this issue basically: https://github.com/GoogleChrome/lighthouse/issues/6512#:~:te... . Tried all of the proposed solutions and this error still pops up on certain sites and certain configuration settings. Felt totally random when it started happening.

Do you have a good record of these sites/configurations? We suspect it's related to the host environment in some way that we can't reproduce on our machines. It'd be useful information for debugging if you can share it. Thanks!

Re: Google Lighthouse V8 – Improved CLS metrics

#53

Post by hoten » Thu, Jun 03, 2021, 4:33 PM UTC

jffry wrote: post #31

It's good to see that they've added a Content-Security-Policy related test. I checked and Lighthouse 8.0.0 still penalizes you on "best practices" if your CSP does not allow inline styles. Something that Lighthouse injects for testing tap-targets has inline styles, and Chrome will log a warning to the console, and Lighthouse penalizes you for that: https://github.com/GoogleChrome/lighthouse/issues/11862

This admittedly slipped our minds. We'll be sure to fix this for the next release. Thanks for the reminder.

Re: Google Lighthouse V8 – Improved CLS metrics

#54

Post by hoten » Thu, Jun 03, 2021, 4:35 PM UTC

rhdunn wrote: post #10

Is there a way to run lighthouse 8.0.0 on older versions of Chrome for local (development) websites, so we can test them now instead of waiting until Chrome 93 is released?

In addition to the other comment, you could also install Chrome Canary to use the latest Lighthouse + Chrome.

If you don't have Canary installed, the CLI will use Chrome Stable. If Canary is present, that is the default. This can be configured with CHROME_PATH.

Re: Google Lighthouse V8 – Improved CLS metrics

#55

Post by nness » Thu, Jun 03, 2021, 4:46 PM UTC

This explains why our Lighthouse score went from 100 to 67 overnight with marginal code changes... Phew

Re: Google Lighthouse V8 – Improved CLS metrics

#56

Post by Aissen » Thu, Jun 03, 2021, 4:54 PM UTC

hoten wrote: post #50

Aissen wrote: post #12

It seems Accessibility measurement broke on web.dev/measure (the report mentions lighthouse 8.0.0): Background and foreground colors have a sufficient contrast ratio - Error! axe-core Error: Cannot read property 'filter' of undefined This website had ~80 in accessibility before. Edit: this issue was known before release: https://github.com/GoogleChrome/lighthouse/issues/11384

All of the reported URLs showing this issue no longer do, in the latest version of Lighthouse or on web.dev. Can you provide the URL (either here or in that issue) for which you still get this error? Thanks!

Sure. Just commented on the bug report.

Re: Google Lighthouse V8 – Improved CLS metrics

#57

Post by jffry » Thu, Jun 03, 2021, 4:58 PM UTC

hoten wrote: post #53

jffry wrote: post #31

It's good to see that they've added a Content-Security-Policy related test. I checked and Lighthouse 8.0.0 still penalizes you on "best practices" if your CSP does not allow inline styles. Something that Lighthouse injects for testing tap-targets has inline styles, and Chrome will log a warning to the console, and Lighthouse penalizes you for that: https://github.com/GoogleChrome/lighthouse/issues/11862

This admittedly slipped our minds. We'll be sure to fix this for the next release. Thanks for the reminder.

Thanks! It's not a huge issue, just moderately amusing. Thanks for the work on Lighthouse.

Re: Google Lighthouse V8 – Improved CLS metrics

#58

Post by [deleted] » Thu, Jun 03, 2021, 5:43 PM UTC

tasogare wrote: post #45

robin_reala wrote: post #20

Earlier quoted context omitted.

HN uses JS for the voting buttons.

It also has ads. Few, limited to YC companies, but ads nonetheless.

[deleted]

Re: Google Lighthouse V8 – Improved CLS metrics

#59

Post by pupppet » Thu, Jun 03, 2021, 9:56 PM UTC

IMTDb wrote: post #9

Possiblyheroin wrote: post #5

This is so exhausting, infuriating and perplexing. Just 1 week after managing to claw our LightHouse score up to 90 - its shot back down 72. The arbitrary nature of their weighting is just tiring - and its compounded by the fact that noone actually knows how much this actually impacts SEO.

Looks to me that you are not. using Lighthouse for the right reasons. Lighthouse isn't there to improve your SEO. It's just a set of heuristics that make you website performance - as perceived by end users - measurable, and thus improvable. They add a quantitative score on a very qualitative process. If you clawed your Lighthouse score to 90, you should have improved your end users experience, and that's what matters…

Google needs to market Lighthouse to only developers. No good comes from your customers running these tests.

Re: Google Lighthouse V8 – Improved CLS metrics

#60

Post by tills13 » Thu, Jun 03, 2021, 10:21 PM UTC

hoten wrote: post #51

tills13 wrote: post #46

Is CLS still broken for single page apps?

Can you elaborate? If you are referring to the long duration of a SPA, we resolved that by making CLS windowed: https://web.dev/evolving-cls/

Yes that is what I was referring to. Do you know if the Chrome User Experience report will use this windowing?