All posts
Engineering · Performance
The Next.js performance checklist we use on every launch
By Gravityy Studio · · 6 min read
LCP under 2.5s and Lighthouse 90+ aren't luck. They're the result of a repeatable checklist. Here's ours.
Performance is a feature. Faster pages rank better, convert better and cost less to serve. This is the checklist we run before every launch.
Rendering
- Prefer static generation and ISR for marketing pages; render dynamically only what's personal.
- Keep client components at the leaves. Server Components ship zero JavaScript.
- Lazy-load heavy, below-the-fold experiences like 3D scenes and charts.
Images & fonts
- Use
next/imagewith explicit sizes and modern formats. - Load fonts with
display: swapand subset them. - Make sure the LCP element is text or a priority image, never a canvas.
JavaScript
- Audit bundles. A single heavy dependency can undo all your work.
- Defer analytics until after consent and after the page is interactive.
Measure in the field
Lab scores are a starting point. Track Core Web Vitals from real users and fix regressions in CI.
| Metric | Target |
|---|---|
| LCP | < 2.5s |
| INP | < 200ms |
| CLS | < 0.1 |
Fast by default, measured continuously: that's the standard.
Read next
How to build a lead generation system (not just a website)