9 ms·
Google Lighthouse V8 – Improved CLS metrics
- adamsvystun 5y agoFunnily 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 :)
- deleted 5y ago[deleted]
- dmix 5y agoCurious how HN itself stands now.
- rozenmd 5y agoPretty well on performance: https://onlineornot.com/perf-results/bZe4p1de7R.html https://onlineornot.com/perf-results/bZe4p1de7R.html
- andy_ppp 5y agoWell, clearly sites with no images or ads or javascript will score highly!
- robin_reala 5y agoHN uses JS for the voting buttons.
- bqmjjx0kac 5y agoI assume also for thread collapsing. For some reason, it is pretty slow on large threads.
- ehsankia 5y agoYeah 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.
- tasogare 5y agoIt also has ads. Few, limited to YC companies, but ads nonetheless.
- deleted 5y ago[deleted]
- manojlds 5y agoWhy? HN is one of the most bare bones and barely usable sites.
- polyvisual 5y agoha, yes, absolutely. That shift of content is beyond frustrating.
- gempir 5y agoI tried so many ways to avoid that "feature" but they keep changing their implementation every few weeks. It's super frustrating. This is my current uBlock filter against it, I think it still works? google.com#?#div:has( > div > div > h4:-abp-contains(People also))
- johtso 5y agoThis trips me up at least a few times a week. Infuriating!
- bobbylarrybobby 5y agoAnd some PM is probably looking at those misclicks and seeing “engagement”
- tootie 5y agoI'm guessing google search doesn't care about SEO
- mimsee 5y agoAnd on mobile Google likes to switch the order of the nav buttons: "All, Images, Maps" to "All, Maps, Images" depending on the search query.
- stefanfisk 5y agoThey 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".
- rozenmd 5y agoIf you're running Google Lighthouse manually, you might want to check out a tool I'm building - https://OnlineOrNot.com https://OnlineOrNot.com - it automatically monitors your page speed (as well as uptime, and soon Puppeteer checks). It uses Google Lighthouse v8.0.0 as of this morning (Australian time). We have a free tier with no time limit or credit card required, if you want to check it out.
- Possiblyheroin 5y agoThis 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.
- madeofpalk 5y agoIs there any indication that Lighthouse affects SEO at all?
- synthmeat 5y agoWhen it completely rolls out during this month, it's going to be tie-breaker which, supposedly, happens a lot more often than people think. Additionally, it's not the Lighthouse score that you need to worry about, but WebVitals (FID, LCP, CLS) and only that for Field data, if your main concern is SEO. Lighthouse is just a general tool that can hint you at performance issues.
- rozenmd 5y agoYour performance affects SEO, and people take the Performance Score as measured by Google Lighthouse to be a proxy for how Googlebot will rank their site.
- dr-detroit 5y agoYes. This is the wrong place to ask about SEO most of these cats use duckduckgo
- IMTDb 5y agoLooks 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. Your score shot back down to 72, you know have new areas to investigate, super cool ! Your SEO will not suddenly improve or worsen due to this change. If you don't, however, address the new advices given by Lighthouse over a long period of time, other websites will, and their UX will be better than yours. And your SEO will reflect that. But that's the game with technology: over time, technology evolves, requirements change, and expectations shift.
- rhdunn 5y agoIs 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?
- Deukhoofd 5y agoRun the terminal command in the README of the repo on your sites.
- rhdunn 5y agoThat works. Thanks.
- hoten 5y agoIn 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.
- Aissen 5y agoIt 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 https://github.com/GoogleChrome/lighthouse/issues/11384
- hoten 5y agoAll 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!
- hobbescotch 5y agoNot sure if it's just me, but the Lighthouse CLI is so buggy that I've resorted to setting to up to run in a docker container so that it doesn't crash when trying to load certain sites/configurations. Hope that they work on improving stability at some point. That being said, kudos to the team on the release, I'm sure this is a challenging project to work on!
- disasterkitsltd 5y agoIronically I've found the CLI to be the only stable channel of Lighthouse. What do you see that docker fixes?
- hobbescotch 5y agoFixes this issue basically: https://github.com/GoogleChrome/lighthouse/issues/6512#:~:text=PROTOCOL_TIMEOUT%20refers%20to%20the%20situation,uses%20to%20talk%20to%20Chrome 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.
- InternalRun 5y agoI’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.
- hoten 5y agoDo 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!
- jffry 5y agoIt'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 https://github.com/GoogleChrome/lighthouse/issues/11862
- anti-nazi 5y agoanyone noticed that ycombinator is a white supremacist network?
- deleted 5y ago[deleted]
- tills13 5y agoIs CLS still broken for single page apps?
- hoten 5y agoCan 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/ https://web.dev/evolving-cls/
- CalChris 5y agoThe title's use of V8 is misleading because Google uses the name V8 to refer to its Javascript engine. It should be v8.0.0.
- nness 5y agoThis explains why our Lighthouse score went from 100 to 67 overnight with marginal code changes... Phew