Next.js Performance Checklist: 12 Fixes That Matter
A practical Next.js performance checklist: keep pages static, ship less client JavaScript, size images correctly, and measure Core Web Vitals in the field.
By UndieGravity, , 2 min read
Most slow Next.js sites are slow for the same few reasons: too much JavaScript in the browser, images without sizes, and pages that render on every request when they could be static. Work through this list from the top; the early items usually give the biggest gains.
Know what you are measuring
Google judges real-user experience with three Core Web Vitals, each measured at the 75th percentile of visits: Largest Contentful Paint (good is 2.5 seconds or less), Interaction to Next Paint (200 milliseconds or less), and Cumulative Layout Shift (0.1 or less). Lab tools like Lighthouse help you debug, but field data in Search Console is what counts.
Rendering
- Keep pages static when the data allows it. A page with no request-time data is prerendered at build and served from a CDN.
- Revalidate instead of rendering on every request. For a catalog that changes a few times a day,
export const revalidate = 60is plenty. - Stream slow parts. Wrap a slow component in
<Suspense>so the rest of the page arrives first.
JavaScript
- Default to Server Components. Add
"use client"only to the components that need state, effects, or browser APIs, and keep those components small. - Import heavy libraries lazily. Charts, editors, and maps can load with
next/dynamicwhen they are actually shown. - Load third-party scripts with `next/script`. Analytics rarely needs to block the page;
afterInteractiveorlazyOnloadis usually enough.
Images and fonts
- Use `next/image` with a correct `sizes` value. Without it, the browser may download a much larger file than it displays.
- Preload only the hero image. Use
preloadon the one image that is the Largest Contentful Paint, not on every image. - Load fonts with `next/font`. It self-hosts the files and sets fallback metrics, which removes layout shift when the font swaps in.
Layout stability
- Reserve space for anything that loads late: images, ads, embeds, and banners. A fixed aspect ratio box is enough.
- Avoid inserting content above what the user is reading, such as a cookie bar that pushes the page down.
- Animate `transform` and `opacity` only. Animating
width,height, ortopforces layout on every frame.
Check your work
Run next build and look for routes marked as dynamic that you expected to be static. Then deploy and watch the Core Web Vitals report in Google Search Console for a few weeks, since field data updates slowly.
Run this checklist on any template you start from too. Open a template, clone it, and run next build to see which routes are static before you add your content.