Stuck on an issue?

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.

Help with understanding LCP metrics

See original GitHub issue

Hi 👋

We are facing with large LCP metrics on www.powerthesaurus.org. And we even can’t get why does this happen.

According to the trace that I see in the Lighthouse report, almost all the content is shown right after page load (especially the main content). But LCP is postponed far away.

Profile-20200608T190653.json.zip

Can you give us a bit of advice from where to start?

Issue Analytics

State:
Created 3 years ago
Comments:5

Top GitHub Comments

1reaction

patrickhulcecommented, Jun 9, 2020

Glad you found the issue!

The only question I have now is why this highlighted header block is treated as LCP?

That appears to legitimately be the largest text node on the page and there are no large images.

If there are no further problems, I’m going to go ahead and close this out but feel free to come back if you believe there’s something Lighthouse needs to change 😃

1reaction

ElForasterocommented, Jun 9, 2020

@patrickhulce Finally, the root of the problem was found. We had an extra top-level <Suspense /> component in our App that shouldn’t be in the production build. Despite the fact, there weren’t any async-loading components during initial rendering, this extra <Suspense /> caused such strange behavior.