Hi @webepc,
This is the nature of the consent banner in general. It mostly loads last, above the fold and on mobile it has the most real estate on the screen.
The lighthouse API for these reports accesses the website as first time visitor and sees the banner. You could make the banner smaller to get another LCP for this specific request, but I think the Chrome UX Reports they’re using with real-time monitoring doesn’t really see the banner that often.
I wouldn’t be to worried about this specific metric, but if you want to improve it I would suggest making the text shorter so it’s DIV doesn’t show up as LCP.
I’m not a fan of making things smaller to cut directly in the usability of the banner itself, which negates the purpose of any UX improvements this metric should have.
There are also ways to not make it show up for Lighthouse report, for example sliding it in the viewport at the right moment to circumvent this metric, but that’s also not really how this should work.
This is an example of an even bigger text banner, but the LCP is an image: https://pagespeed.web.dev/analysis/https-jixenomorph-nele-instawp-xyz/x9q6vr2e75?hl=IT&form_factor=mobile. The endgame is to improve perceived pagespeed, which this does. The banner does not cover the page loading above fold, so pagespeed is quick for the user.
In the end, I think this specific metric is important but only when the problem is consistent in the real-world, and this is isolated to the API. But it’s your choice, you can set the text to “To provide the best experiences, we and our partners use technologies like cookies to store and/or access device information.” on font-size: 12px; for example and check the results.
Let me know if you have any questions, regards Aert
