LCP < 2.5s, INP < 200ms, CLS < 0.1. Use field data from Chrome UX Report. These are confirmed ranking signals.
Focus on field data (real users) from CrUX, not just lab data from Lighthouse. A page can score 100 in Lighthouse but still fail CWV in the field due to real-world network conditions and device variety.
Don't chase a perfect Lighthouse score. The ranking signal uses field data (Chrome User Experience Report) at the 75th percentile. Lab data is just for debugging.
Go to pagespeed.web.dev and test your homepage, top landing pages, and key conversion pages. Pay attention to the "Field Data" section (real users) more than "Lab Data". Screenshot results as your baseline.
LCP (Largest Contentful Paint) is usually your hero image or main heading. Target: under 2.5 seconds.
INP (Interaction to Next Paint) measures responsiveness. Target: under 200ms. Most INP issues come from heavy JavaScript blocking the main thread.
CLS (Cumulative Layout Shift) measures visual stability. Target: under 0.1. Layout shifts frustrate users and hurt rankings.
Go to Search Console > Experience > Core Web Vitals. Check both mobile and desktop. Google groups URLs by similar template, so fixing one template page fixes the whole group.
Here is my Lighthouse/PageSpeed Insights report for [URL]: [PASTE REPORT DATA] Analyze the report and provide: 1. Specific fixes for each Core Web Vital that's failing 2. Code snippets for implementing lazy loading, image optimization, and critical CSS 3. A prioritized checklist of performance improvements 4. Estimated impact of each fix on LCP/INP/CLS 5. Server-side optimizations I should consider
Track your progress and get guided through every step.
Open Interactive Tool