Helpdesk is open from Monday through Friday CET
We have one more question.
The loading times can be seen in the screenshots.
The test SVG of the 4SEO component has by far the longest loading time.
Is that the reason why the LCP value is bad? It says 2500 ms in 15 measurements.
When Google visits the page, it will also measure the bad value of your SVG!?
Regards!
Hi
The loading times can be seen in the screenshots.
The test SVG of the 4SEO component has by far the longest loading time.
Nope, the loading time on your screenshot is very quick.The longest loading time for an image is this one:
The loading time is not 163ms. 163ms is the time at which the image download started. We inject the img tag 3 seconds after the page load, exactly for this reason, to avoid affecting the page load time.
Is that the reason why the LCP value is bad? It says 2500 ms in 15 measurements.
No. This SVG has no size (it has width=0 and height=0), and so it does not affect LCP, which is the "largest contentful paint". What defines LCP is the time it takes for the largest element on your page to be displayed. Can be an image, can be a large div with lots of content. This time also includes the page rendering time from your server.
When Google visits the page, it will also measure the bad value of your SVG!?
The value for that SVG is good, very good. There's no problem here.
Best regards
Yannick Gaultier
weeblr.com / @weeblr
Thank you for your detailed explanation!
Hi
You're welcome! To identify what's causing a HIGH LCP, you should use the Dev tools in Chrome, more specificaly the Lighthouse tab.
Go to the page you want to analyze and then run "Generate report" on the Lighthouse tab (you can only check the "Performance" option, else the diagnostic may be longer). Then scroll down to the "Diagnostics" section and you'll see an item called "Largest Contentful Paint element".
This will tell you which is the HTML element on that page that was used to compute the LCP number.
You still need to look at the "Waterfall" to know what's the TTFB (Time to first byte) of that page.
TTFB is the time it took your server to respond with the page content. When the browser gets the page content, it can start fetching the CSS, javacript and images (let's call that Transfer time) , and then start displaying the actual page, up to the point where the largest element on the page is displayed (let's call that additional time: Display time).
So your LCP time as measured by Google is TTFB + Transfer Time + Display time. Usually the biggest parts are TTFB and Transfer time, and that's also where you can more easily do things.
Best regards
Yannick Gaultier
weeblr.com / @weeblr
