The main content appears slowly: LCP 4200 ms on 2 pages
On the listed pages, Largest Contentful Paint, the time until the largest image or text block in view is shown, is above 2.5 seconds (over 4 seconds is poor). Make that element arrive first: a compressed, correctly sized hero image that is not lazy-loaded, less render-blocking CSS and JavaScript, and a fast server response.
What it means
Largest Contentful Paint is how long the biggest element takes to show; Google counts up to 2500 ms as good. Compress and size the hero image, serve it early (preload, no lazy loading above the fold) and cut render-blocking CSS and JavaScript.
Why it matters for AI search
LCP is one of Google's Core Web Vitals, the measures it uses for page experience, and it is how visitors judge whether a page is fast. On slow pages people leave before they read anything.
The audit asks Google PageSpeed Insights for mobile results of the start page and the most linked pages. It uses real-user data from the Chrome UX Report (the 75th percentile over the last 28 days) for the page, or else for the whole site, and a Lighthouse lab run when there is none; the evidence shows which. The finding is P2 when any page is in the poor range.
How to fix it
- Run PageSpeed Insights on a listed page and see which element is the LCP element and where its time goes: server response, load delay, load time or render delay.
- If it is an image, compress it, serve a modern format such as WebP or AVIF at the size it is shown, remove
loading="lazy"from it and addfetchpriority="high". - If it is text, make sure fonts and CSS do not hold it back: inline the critical CSS, use
font-display: swapanddeferscripts that the first view does not need. - If the server response is slow, see the TTFB guide: page caching and a CDN help most.
- Run the site audit again from your account. Lab results change at once; real-user data can take up to four weeks to reflect a fix.
Example
<link rel="preload" as="image" href="/img/hero-1200.webp" fetchpriority="high">
<img src="/img/hero-1200.webp" width="1200" height="600"
fetchpriority="high" alt="Product dashboard">
<script src="/js/app.js" defer></script> How to confirm the fix
After the change, press "Check again" on the report: it lists what was fixed and how the score changed.