Core Web Vitals fix serviceTurn “Core Web Vitals: Failed” into a pass.

The assessment at the top of PageSpeed Insights uses field data: real visits from the last 28 days. It fails if any one of the three metrics is outside the good range at the 75th percentile. The performance score underneath comes from a single lab test on a simulated phone, which is useful for debugging but is not what Google’s ranking systems use.

That is why a page can score 95 in the lab and still fail. Real visitors use slower phones and networks, arrive with cold caches, and click things the lab never touches, which is where INP problems live. If your page does not have enough traffic for its own field data, PageSpeed Insights shows your whole site’s data instead, or nothing at all.

• Find the LCP element first. It is usually the hero image or headline. Everything else is secondary.
• Never lazy-load it. Give the LCP image fetchpriority="high", correct dimensions, and a modern format like AVIF or WebP.
• Make it discoverable. If the image is set in CSS or loaded by JavaScript, the browser finds it late. Put it in the HTML, or preload it.
• Cut server response time. Slow TTFB delays everything. Caching full pages at a CDN often halves LCP on its own.
• Remove render-blocking resources. Inline the critical CSS, defer the rest, and load fonts without blocking text.

• Find the slow interactions. Real-user data shows which clicks are slow. Common culprits: menus, filters, add-to-cart buttons, and forms.
• Break up long tasks. Any JavaScript task over 50 ms blocks the next paint. Split the work and yield to the browser between chunks.
• Update the screen first. Show the visual response immediately, then do analytics, network calls and heavy logic afterwards.
• Audit third parties. Chat widgets, A/B testing tools and tag managers often run expensive code on every click.
• Reduce hydration cost. On React and Next.js sites, less client-side JavaScript means a faster main thread.

• Reserve space for media. Set width and height, or an aspect ratio, on every image, video and embed.
• Reserve space for late content. Cookie banners, promo bars and ads should have a fixed slot, or overlay the page instead of pushing it down.
• Stop font swaps from jumping. Preload the main font and use a size-matched fallback so text does not reflow when it loads.
• Animate with transforms. Moving elements with transform never shifts layout. Changing top, height or margin does.

Google says Core Web Vitals are used by its ranking systems, and also that great, relevant content matters more. In practice they act as a tie-breaker between similar pages, and they matter most on competitive queries where everyone’s content is good.

The bigger payoff is usually conversions. In the Deloitte study “Milliseconds Make Millions”, commissioned by Google, a 0.1 second faster mobile site lifted retail conversions by 8.4% and travel conversions by 10.1%. Faster pages are cheaper to advertise, too, because landing page experience feeds into Google Ads Quality Score.

Lab scores improve the moment fixes go live. Field data takes longer, because it is a 28-day rolling window: it shifts gradually as new, faster visits replace old ones. Search Console’s “Validate fix” process monitors for about 28 days too. That is why this service includes a follow-up check a month after delivery.