S.
  • Services
  • For you
  • Solutions
  • Work
  • About
  • Know-how
  • Blog
Start a project
EN/PL/RU
  • Services01
  • For you02
  • Solutions03
  • Work04
  • About05
  • Know-how06
  • Blog07
Start a project
EN/PL/RU
Vlad Sedenko
Independent web product developer
EU / Poland / Warsaw
Products
  • NextWooNext.js storefront for WooCommerce
© 2026. All rights reserved
Services
  • Product Discovery
  • UX/UI Design
  • MVP Development
  • SaaS Development
  • Website Redesign
  • Web Application Security
  • Conversion Optimization
  • API Integrations & Business Automation
  • Product Support
Explore
  • Services
  • For you
  • Work
  • Solutions
  • About
  • Blog
  • Know-how
  • Contact
Start a project
  • vlad@sedenko.net
  • LinkedIn
  • Privacy/Cookies
Know-how/Next.js SEO Checklist: The Complete Guide for App Router (2026)

Part 8 of 22

Core Web Vitals: the three numbers Google measures

LCP, INP and CLS in Next.js: concrete fixes for each metric, lab vs field data, and wiring real-user monitoring with useReportWebVitals.

2026-07-15
Core Web Vitals: the three numbers Google measures

All topics in this guide

A practical, section-by-section SEO checklist for Next.js: rendering strategy, Metadata API, hreflang, structured data, Core Web Vitals, and optimization for AI answer engines.

Core Web Vitals are a confirmed ranking signal and, more importantly, a conversion factor. The current trio:

  • LCP (Largest Contentful Paint) — main content visible in < 2.5s. Fixes: static/ISR rendering, priority hero image, minimal render-blocking CSS, fast TTFB (see Rendering strategy).
  • INP (Interaction to Next Paint) — replaced FID in March 2024; every interaction should respond in < 200ms. Fixes: fewer/lazier third-party scripts, smaller client bundles ("use client" only where needed), breaking long tasks.
  • CLS (Cumulative Layout Shift) — < 0.1. Fixes: dimensions on all images/embeds, reserved space for banners and ads, next/font (no font-swap jumps).

Measure both ways:

  • Lab: Lighthouse in CI (e.g. @lhci/cli on every PR) catches regressions before deploy.
  • Field: real-user data is what Google actually ranks on. Wire it up in one hook:
// app/web-vitals.tsx
"use client";
import { useReportWebVitals } from "next/web-vitals";

export function WebVitals() {
  useReportWebVitals((metric) => {
    // send to your analytics endpoint
    navigator.sendBeacon("/api/vitals", JSON.stringify(metric));
  });
  return null;
}

Check field data in Search Console → Core Web Vitals, or PageSpeed Insights (which shows CrUX data when available).

Checklist:

  • LCP < 2.5s, INP < 200ms, CLS < 0.1 in field data, not just Lighthouse
  • Lighthouse CI or equivalent guarding against regressions
  • useReportWebVitals feeding real-user metrics to your analytics
  • Mobile checked separately — that's where most sites fail
← PreviousImages, fonts and scripts: the classic performance trioNext →Redirects, 404s and status codes

01—22

All topics in this guide

  1. 01Rendering strategy: what does the crawler actually see?→
  2. 02Metadata API: titles, descriptions and the template pattern→
  3. 03Canonical URLs and hreflang: one page, one address→
  4. 04Open Graph and dynamic OG images→
  5. 05sitemap.ts and robots.ts: file conventions instead of hand-written XML→
  6. 06Structured data: JSON-LD that earns rich results→
  7. 07Images, fonts and scripts: the classic performance trio→
  8. 08Core Web Vitals: the three numbers Google measures•
  9. 09Redirects, 404s and status codes→
  10. 10Caching and content freshness→
  11. 11AEO/GEO: getting cited by ChatGPT, Perplexity and Google AI Overviews→
  12. 12Monitoring: SEO is a loop, not a launch task→
  13. 13Trust and E-E-A-T: making your site believable→
  14. 14Image SEO: turning pictures into traffic→
  15. 15Internal linking and site architecture→
  16. 16Search intent: pages that match what people actually type→
  17. 17Programmatic SEO in Next.js: pages at scale without the spam→
  18. 18SEO migration: replatforming to Next.js without losing traffic→
  19. 19Pagination and faceted navigation without index bloat→
  20. 20Accessibility and SEO: one job, two rewards→
  21. 21Content decay: refresh, consolidate or prune→
  22. 22Off-page for developers: earning links without buying them→

Want this handled for you?

I audit and fix technical SEO on Next.js sites — indexing, performance, hreflang and AI visibility.

Technical SEO service