31–40 of 63 posts
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
Earlier quoted context omitted.
All the publishers I know (being one myself) only care about CWV for SEO.
Of course they do, but if that's the proxy metric that makes them care about usability and user experience, it's a win-win.
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 :)
Earlier quoted context omitted.
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…
> Your score shot back down to 72, you know have new areas to investigate, super cool ! I generally do not find it "super cool" when I suddenly/unexpectedly have new areas to investigate. In most cases, the developer dealing with lighthouse scores is someone who just built a website to a client's spec, only to find out that there are things that it flags which are very time consuming to deal with. Set expectations al…
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 :)
Not 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!
Not 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!
Ironically I've found the CLI to be the only stable channel of Lighthouse. What do you see that docker fixes?
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.
Earlier quoted context omitted.
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's Web Vitals page tracks things like Cumulative Layout Shift (CLS), First Contentful Paint (FCP), and Largest Contentful Paint (LCP). -- All of those metrics are visible in the Performance tab and are recorded by lighthouse. From [1]: "The first reason is that cumulative layout shift will become a ranking factor in May 2021." [1] https://huckabuy.com/2020/12/30/introduction-to-cumulative-l...
Also it hasn't happened yet. They pushed the implementation date to a slow rollout starting in "mid-June"