Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Lighthouse V8 – Improved CLS metrics

github.com

Post reply on HN
Print view View original

41–50 of 63 posts

Re: Google Lighthouse V8 – Improved CLS metrics

#41

Post by mimsee »

adamsvystun wrote: post #2

Funnily enough the biggest offender of Cumulative Layout Shift (CLS) metric in my daily life is google search with its "people also search for" feature that causes me to constantly misclick. Lighthouse is great though :)

And on mobile Google likes to switch the order of the nav buttons: "All, Images, Maps" to "All, Maps, Images" depending on the search query.

Re: Google Lighthouse V8 – Improved CLS metrics

#42

Post by InternalRun »

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.

I’ve experienced the same as you, I’ve lost many hours to fixing different protocol time out errors. We’re running it in ECS now and it’s pretty stable, every now and then one pops up but is fixed by retrying the job.

Re: Google Lighthouse V8 – Improved CLS metrics

#44

Post by stefanfisk »

mimsee wrote: post #41
adamsvystun wrote: post #2

Funnily enough the biggest offender of Cumulative Layout Shift (CLS) metric in my daily life is google search with its "people also search for" feature that causes me to constantly misclick. Lighthouse is great though :)

And on mobile Google likes to switch the order of the nav buttons: "All, Images, Maps" to "All, Maps, Images" depending on the search query.

They do that on desktop as well, and I hate them for it. For anyone who's never noticed it, try googling "backpack" and then "backpacker".

Re: Google Lighthouse V8 – Improved CLS metrics

#47

Post by ehsankia »

bqmjjx0kac wrote: post #40
robin_reala wrote: post #20

Earlier quoted context omitted.

HN uses JS for the voting buttons.

I assume also for thread collapsing. For some reason, it is pretty slow on large threads.

Yeah I looked at the code once and I believe it was recursively collapsing every single comment under when you clicked collapse, and also storing the state of each in localstorage I think. It didn't quite make sense. I think it has been fixed though it's much faster now.

Also not sure when we're finally get non-paginated page loads.

Re: Google Lighthouse V8 – Improved CLS metrics

#49

Post by dr-detroit »

madeofpalk wrote: post #6
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.

Is there any indication that Lighthouse affects SEO at all?

Yes. This is the wrong place to ask about SEO most of these cats use duckduckgo

Re: Google Lighthouse V8 – Improved CLS metrics

#50

Post by hoten »

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!
Post reply on HN