NHRepon
Home
Services
All ServicesWeb Application DevelopmentMobile Application DevelopmentDigital Marketing and SEO
ProjectsToolsProductsPostsAboutContactLogin
HomeServicesProjectsToolsProductsPostsAboutContact
  • Home
  • Projects
  • Posts
Home/Posts/Core Web Vitals optimization guide for Next.js and React apps

Core Web Vitals optimization guide for Next.js and React apps

Core Web Vitals optimization guide for Next.js and React apps
Md. Nur Hossain ReponWeb DevelopmentOct 20, 20264 min read0 Comments
  • Key takeaways
  • What Core Web Vitals measures
  • The fixes that usually move the number
  • Symptom, cause and fix
  • How to measure it properly
  • A practical example
  • Common mistakes
  • A 30-day improvement plan
  • Field data vs lab data
  • Set a performance budget
  • Third-party script policy
  • Frequently asked questions
  • Sources and further reading
  • Related reading

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

SymptomLikely causeWhat to do
Slow LCPServer response, render-blocking assets or a late hero imageImprove TTFB, preload the hero, remove blocking CSS/JS
High INPLong tasks, hydration or heavy event handlersSplit tasks, reduce client JS, defer non-urgent updates
High CLSUnsized media, late fonts or injected bannersSet dimensions, reserve space, use font fallbacks
Good lab, poor fieldLab device and network differ from real usersUse CrUX/Search Console and segment by device and route

How to measure it properly

  1. Use field data. Check the Chrome UX Report or Search Console Core Web Vitals report for the 75th percentile.
  2. Reproduce the worst route. Run PageSpeed Insights and Lighthouse on the actual URL, not a local build.
  3. Record a performance trace. Use Chrome DevTools to find long tasks, render-blocking requests and layout shifts.
  4. Fix one bottleneck. Change one thing, deploy and compare field data after enough traffic.
  5. 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

  1. Week 1. Collect field data and pick the worst route. Write down the baseline.
  2. Week 2. Fix the largest bottleneck and deploy behind a normal release.
  3. Week 3. Test on a mid-range phone and a throttled connection; fix regressions.
  4. Week 4. Compare field data, document the change and add a monitor or budget.

Field data vs lab data

SourceWhat it tells youHow to use it
Field dataWhat real users experiencedThe source of truth for the metric
Lab testA reproducible diagnosisFind the cause and test a fix
Synthetic monitoringAvailability and regressions over timeAlert on a budget breach
RUM segmentationDevice, country and route differencesTarget the worst segment
Server timingDatabase, cache and render timeSeparate backend from frontend

Set a performance budget

BudgetExample starting pointWhy
LCP2.5s or less at p75The main content must appear quickly
INP200ms or less at p75Interactions must feel responsive
CLS0.1 or less at p75Layout movement erodes trust
JavaScriptA route-level KB budgetPrevents bundle creep
ImagesResponsive sizes and modern formatsThe largest common payload
Third-party scriptsA named owner and a capUncontrolled 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

  • Next.js performance checklist
  • Performance optimisation service

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.

Start a short, no-pressure conversation →

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.

#next.js#react#web development
0 Likes6 Views0 Shares
Share:

Related Posts

How to Deploy a Next.js App to cPanel Shared Hosting
adminOct 17, 2026
Web Development

How to Deploy a Next.js App to cPanel Shared Hosting

216 views5 likes2 shares
Hire a Full-Stack Developer in the UK: a buyer's guide
adminOct 18, 2026
Web Development

Hire a Full-Stack Developer in the UK: a buyer's guide

5 views0 likes0 shares
Next.js 15 new hooks and features deep dive 2026
adminOct 18, 2026
Web Development

Next.js 15 new hooks and features deep dive 2026

12 views0 likes0 shares
Migrate jQuery to React 2026 cost guide
adminOct 18, 2026
Web Development

Migrate jQuery to React 2026 cost guide

9 views0 likes0 shares

Leave a Comment


0/2000

Comments

No comments yet.

On this page

  • Key takeaways
  • What Core Web Vitals measures
  • The fixes that usually move the number
  • Symptom, cause and fix
  • How to measure it properly
  • A practical example
  • Common mistakes
  • A 30-day improvement plan
  • Field data vs lab data
  • Set a performance budget
  • Third-party script policy
  • Frequently asked questions
  • Sources and further reading
  • Related reading

NHRepon


Md. Nur Hossain Repon expert in NextJS, React, React Native and Flutter. He is a full-stack web and mobile application developer with 5+ years of experience and a passion for building innovative and robust application. Also, he has a strong background in developing high-quality web and mobile applications using the latest technologies and frameworks.
Let's build something amazing together 🚀

Quick Links


  • About
  • Projects
  • Services
  • Contact
  • Posts
  • Products
  • Privacy Policy
  • Terms of Service
  • Tools
  • Smart Life Hubs

Newsletter


We respect your privacy. Unsubscribe anytime.

Connect


© 2026 NHRepon. All rights reserved.

Build v1.5.4+56.73c4a90