LCP is usually the hero image, headline or video poster. The fix is rarely one trick: you have to reduce the server response, remove render-blocking work and make the largest element load early.
Key takeaways
- Target: LCP ≤ 2.5s 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 Largest Contentful Paint measures
The browser reports the render time of the largest image or text block in the viewport. LCP is split into four phases: time to first byte, resource load delay, resource load time and element render delay.
The fixes that usually move the number
- Improve TTFB with caching, a CDN and a fast database query.
- Preload the hero image and serve it in the right size and format.
- Avoid lazy-loading the LCP image or hiding it behind a client-side fetch.
- Remove render-blocking CSS and defer non-critical scripts.
- Use
font-display: swapand preload the font used above the fold.
Symptom, cause and fix
| Symptom | Likely cause | What to do |
|---|---|---|
| Hero image arrives late | Lazy loading, large file or slow CDN | Use priority, correct sizes, AVIF/WebP and a CDN |
| Text waits for JavaScript | Client-only rendering or a blocking data fetch | Render the hero on the server and stream the rest |
| Slow TTFB | Uncached database query or distant origin | Cache the page, move the origin and add a CDN |
| Image loads but appears late | Layout shift or a CSS animation | Reserve space and avoid opacity/transform delays |
How to measure it properly
- Identify the element. Use PageSpeed Insights or the Performance panel to see which element is the LCP.
- Break down the phases. Check TTFB, resource load delay, load time and render delay separately.
- Test the real URL. A local production build may not reproduce CDN, image or database latency.
- Fix the largest phase. Do not optimise images if the real problem is a 2-second server response.
- Compare field data. Use CrUX or Search Console after the change has enough traffic.
A practical example
import Image from "next/image";
<Image
src="/hero.webp"
alt="Product dashboard"
width={1600}
height={900}
priority
sizes="(max-width: 768px) 100vw, 1200px"
/>
Common mistakes
- Adding
priorityto every image, which competes with the real hero. - Serving a 3000px image to a 390px phone.
- Using a client-side carousel for the first screen.
- Fixing the image while the server response remains slow.
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 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
- Optimise Largest Contentful Paint (web.dev)
- Next.js image optimisation (nextjs.org)
- Image optimisation (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, “LCP optimization guide for Next.js and React apps”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/lcp-optimization-guide-for-next-js-and-react-apps.





Comments
No comments yet.