Core Web Vitals are three field metrics that describe loading, responsiveness and visual stability. Treat them as product metrics: a fast lab score with a slow field score is still a slow experience for real users.
Key takeaways
- Target: LCP ≤ 2.5s, INP ≤ 200ms and CLS ≤ 0.1 at the 75th percentile.
- Measure field data before choosing a fix.
- Change one bottleneck at a time and re-measure on a mid-range phone.
- A fast lab score is not a substitute for real-user data.
What Core Web Vitals measures
LCP measures when the main content appears, INP measures the latency of interactions, and CLS measures unexpected layout movement. Google evaluates them at the 75th percentile of real page views, split between mobile and desktop.
The fixes that usually move the number
- Measure field data first, then use lab tools to reproduce the worst pages.
- Reduce the JavaScript needed for the first screen and defer the rest.
- Serve the hero image and critical fonts from the same origin or a fast CDN.
- Reserve space for images, embeds and dynamic content to prevent shifts.
- Keep third-party scripts out of the critical path and audit them quarterly.
Symptom, cause and fix
| Symptom | Likely cause | What to do |
|---|---|---|
| Slow LCP | Server response, render-blocking assets or a late hero image | Improve TTFB, preload the hero, remove blocking CSS/JS |
| High INP | Long tasks, hydration or heavy event handlers | Split tasks, reduce client JS, defer non-urgent updates |
| High CLS | Unsized media, late fonts or injected banners | Set dimensions, reserve space, use font fallbacks |
| Good lab, poor field | Lab device and network differ from real users | Use CrUX/Search Console and segment by device and route |
How to measure it properly
- Use field data. Check the Chrome UX Report or Search Console Core Web Vitals report for the 75th percentile.
- Reproduce the worst route. Run PageSpeed Insights and Lighthouse on the actual URL, not a local build.
- Record a performance trace. Use Chrome DevTools to find long tasks, render-blocking requests and layout shifts.
- Fix one bottleneck. Change one thing, deploy and compare field data after enough traffic.
- Monitor continuously. Send web-vitals events to your analytics and alert on regressions.
A practical example
import { onLCP, onINP, onCLS } from "web-vitals";
onLCP((metric) => send("lcp", metric.value));
onINP((metric) => send("inp", metric.value));
onCLS((metric) => send("cls", metric.value));
Common mistakes
- Optimising only the homepage while checkout or the blog template is slow.
- Chasing a perfect Lighthouse score instead of improving field data.
- Lazy-loading the hero image or the font needed for the first screen.
- Adding a third-party tag manager without a performance budget.
A 30-day improvement plan
- Week 1. Collect field data and pick the worst route. Write down the baseline.
- Week 2. Fix the largest bottleneck and deploy behind a normal release.
- Week 3. Test on a mid-range phone and a throttled connection; fix regressions.
- Week 4. Compare field data, document the change and add a monitor or budget.
Field data vs lab data
| Source | What it tells you | How to use it |
|---|---|---|
| Field data | What real users experienced | The source of truth for the metric |
| Lab test | A reproducible diagnosis | Find the cause and test a fix |
| Synthetic monitoring | Availability and regressions over time | Alert on a budget breach |
| RUM segmentation | Device, country and route differences | Target the worst segment |
| Server timing | Database, cache and render time | Separate backend from frontend |
Set a performance budget
| Budget | Example starting point | Why |
|---|---|---|
| LCP | 2.5s or less at p75 | The main content must appear quickly |
| INP | 200ms or less at p75 | Interactions must feel responsive |
| CLS | 0.1 or less at p75 | Layout movement erodes trust |
| JavaScript | A route-level KB budget | Prevents bundle creep |
| Images | Responsive sizes and modern formats | The largest common payload |
| Third-party scripts | A named owner and a cap | Uncontrolled tags are a common regression |
Third-party script policy
- Every script needs an owner, a purpose and a review date.
- Load analytics and marketing tags after consent and after the main content.
- Prefer server-side events where they reduce client JavaScript.
- Test the checkout and sign-up with the full tag set enabled.
- Remove tags that no longer answer a business question.
Frequently asked questions
The target is LCP ≤ 2.5s, INP ≤ 200ms and CLS ≤ 0.1 at the 75th percentile. A single fast test is not enough; use the 75th percentile of real page views and segment by mobile and desktop.
No. Start with the routes that matter to revenue or support: checkout, pricing, sign-up, the main product page and the most-read blog template. A fast homepage with a slow checkout is not a fast site.
It depends on traffic. Low-traffic sites can take weeks to accumulate enough data. Use lab tools for immediate feedback, but keep the field metric as the source of truth.
Often yes. Image dimensions, priority, bundle splits, caching and third-party scripts usually deliver more than a visual refresh. Redesign only after the measurement shows the layout itself is the bottleneck.
Sources and further reading
- Web Vitals (web.dev)
- Optimise Largest Contentful Paint (web.dev)
- Optimise Interaction to Next Paint (web.dev)
- Fix layout shifts (web.dev)
Related reading
Need a performance audit?
Send the URL and the metric that matters. I will identify the bottleneck, the likely fix and the cheapest way to prove it worked.
How to cite this guide: Nur Hossain Repon, “Core Web Vitals optimization guide for Next.js and React apps”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/core-web-vitals-optimization-guide-for-next-js-and-react-apps.





Comments
No comments yet.