Google On Why Google Search Console LCP Is Not Wrong
https:/
Caching should be a "cherry on top" to boost speed, rather than the only reason you have a fast site.
Related contents with similar topics
-
Let's say a SPA first load has been optimized with SSR and the LCP image is loaded pretty fast because it's in the HTML.
But the JavaScript then builds a carousel in the DOM, which initially shows the very same image.
I guess there's a second render of the image. How can I check this easily?
Would it make sense that the LCP takes the late second render of the image, instead of the fast first one?
-
Apparently, an image whose part above the fold is indeed the largest, but of which only a small part can be seen, can be considered an LCP element, even if another image has a larger part visible... 😭
You can see this for my photography site in this WebPageTest result:
https://www.webpagetest.org/vitals.php?test=230606_BiDcN4_4NJ&run=3&cached=0#lcp
-
Limiting the image density on mobile devices drasticaly improves performance, with no visual loss, so we did it!
I still wish it was much easier than dealing with
<picture>andxdescriptors for fluid images… 😞With a
<img maxdensity="2.5" …>attribute for example!If you agree, comment:
https://github.com/whatwg/html/issues/4421 -
Largest Contentul Paint change in Chrome 112 to ignore low-entropy images
This may result in LCP times increasing, if a low-content background was being painted very early, or if a low-content placeholder was being used…
-
Priority Hints and optimizing LCP
Increasing the priority of a resource usually comes at the cost of another resource, so Priority Hints should be used sparingly. However, if the browser…
Kevin Farrugia