Performance & troubleshooting
Core Web Vitals measure real user experience for loading, interaction and visual stability. Fixing them effectively means identifying the element, script or layout behavior that drives the failing metric on representative templates.
Direct answer
Google’s current good thresholds are LCP ≤2.5 seconds, INP ≤200 milliseconds and CLS ≤0.1, evaluated at the 75th percentile of page loads. Field data and lab tools answer different questions and should not be treated as interchangeable.
Current facts
Answer scope
Largest Contentful Paint tracks when the page’s main visible content is likely rendered. On WordPress, the LCP element is often a hero image, heading region or large media block.
Common causes include slow server response, render-blocking CSS, large images, font loading and delayed client-side rendering.
Interaction to Next Paint measures how responsive the page is when users interact. Heavy JavaScript, page-builder runtime, third-party widgets and long tasks can increase INP.
Optimization should isolate the expensive interaction rather than simply defer every script.
Cumulative Layout Shift increases when visible elements move unexpectedly. Missing image dimensions, ad slots, banners, late fonts and injected widgets are common causes.
Reserve space and avoid inserting content above what the user is already reading unless the interface explicitly expects it.
CrUX-based field metrics aggregate real users, while Lighthouse and PageSpeed lab runs simulate controlled conditions. Lab tools are useful for diagnosis but a single run is not the field score.
Low-traffic pages may not have enough public field data and may be grouped at origin level or not reported.
Service pages, articles, product pages and checkout can have different LCP elements and script loads.
Choose URLs that represent traffic and business importance, then verify that fixes do not break forms, analytics or ecommerce behavior.
Questions
Good is currently LCP ≤2.5s, INP ≤200ms and CLS ≤0.1 at the 75th percentile.
No. The lab performance score and real-user Core Web Vitals are related but different measurements.
No. Different templates can have different LCP elements, scripts and layout behavior, so performance work should use representative URLs.
Evidence
First-party platform documentation and clearly labelled public market benchmarks used for factual claims on this page. A source link does not imply endorsement.
Start a conversation
Send the current setup and the result you need. I will review the problem and suggest the most practical next step.