How do I improve my LCP score to meet the Google Core Web Vitals requirements for 2024?

All answers to this question.

LCP is often a battle against the "Main Thread." Even with a CDN, if your hero image isn't using the fetchpriority="high" attribute, the browser might delay it. I recommend checking for "Layout Shifts" from third-party scripts like chatbots or pop-ups that might be pushing the LCP element down. Also, look at your server response time (TTFB); if your hosting is slow, your LCP will never be "Good." Try implementing critical CSS to render the above-the-fold content before the full stylesheet loads.

   Answered 2024-02-16 by Melissa Gardner

Are you using WebP or AVIF formats for your images? Sometimes just switching from high-res JPEGs to a modern format can shave off those critical milliseconds.

   Answered 2024-02-17 by Tyler Bennett

• Tyler, we moved to WebP last month, which helped slightly, but the real issue seems to be a heavy JavaScript bundle from our tracking pixels. I’m currently looking into using a Tag Manager server-side container to move that processing off the client's browser. It’s a bit of a technical hurdle, but it seems like the only way to clear the main thread.

     Commented 2024-02-18 by Jordan Hayes

Check your "Preload" tags. Preloading your LCP image can significantly reduce the time it takes for the browser to discover that specific asset.

   Answered 2024-02-19 by Sarah Jenkins

• Sarah is spot on. A simple tag for the hero image can often be the single most effective "quick fix" for a lagging LCP score.

     Commented 2024-02-20 by Melissa Gardner