Patrick Hulce

We've put together a [project plan and rough design doc](https://docs.google.com/document/d/1fRCh_NVK82YmIi1Zq8y73_p79d-FdnKsvaxMy0xIpNw/edit#) that's open for comments. I've also updated this issue to reflect the early phases of the plan. **IMPORTANT**: This next...

Thanks for filing @CDDelta! I can reproduce and this appears to be a bug in the LCP metric itself, we'll look into it 👍

Thanks @widmanski I can reproduce this as well!

I filed https://bugs.chromium.org/p/chromium/issues/detail?id=1104218 with these details 👍

@danielhaim1 @RaicuRobert @hummal thanks for the clarification! There are many types of pages that receive NO_LCP and this issue only tracks a very specific one (when the LCP element animates...

Also @adamraine from our triage it looks like this is ["WAI" from the LCP spec perspective](https://bugs.chromium.org/p/chromium/issues/detail?id=1104218#c2) which is really unfortunate for us. We're at a dead end. I'll file an...

Thanks for the extra info and the URL @hummal! There's something extra weird going on in Chromium for that URL I filed https://bugs.chromium.org/p/chromium/issues/detail?id=1135165 I can also reproduce your intermittent behavior...

Thanks @widmanski I can also reproduce on a minified version. I'll go back to bug the chromium issue that it's not fixed :) For future issue readers: there are two...

@Hoten where exactly do we stand here? Have we increased the timeout back to 60 and these are just stragglers?

Also the report in #6918 (https://googlechrome.github.io/lighthouse/viewer/?gist=6d3d0224e5ebdaf3b2c787de38a6befa) suggests that some of these cases might be the root cause behind `NO_FCP` as well!