Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Impact of animations on lighthouse v6?
See original GitHub issue*In relation to Lighthouse v6 (in Chrome Canary)
I’ve seen much worse ratios that what I can obtain with v5.6, and what I’m finding is a big impact on any animations present in the front page, where these animations are merely visual
I believe to see that the Largest Contentful Paint (in mobile) seems to finish when any animation ends, as I see in the report a LCP value of ~7s (in this case), even though later in Performance I can see the label LCP appearing at ~800ms
Perhaps somebody could explain a little bit what would be the best way to add animations on the first page without affecting LCP, or if the suggested attitude is to eliminate any animation from the front page (?)
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
All of my Svelte websites with hero animations are showing 10s+ LCP. Some don’t even have images. The actual load times are < 100ms, and this has been driving me bonkers. If there is anything I can do to help get to the bottom of this, some advice would be greatly appreciated!
@ciekawy I didn’t go deeper there
I can say that in my hands having an image (no animation) without React (with 11ty) causes going from 100s to 90s
But with React (with Gatsby) scores are more vulnerable, if I’m between 70s and 80s when there are images involved I’m happy. This is an ongoing issue though
*If you’re using Gatsby, there’s an opened issue about this