sdcorejs-review-performance-nextjs

Run a Next.js performance audit by executing a production build and starting your staging or localhost site on port 3000, then analyzing key routes like home, longest-content, and interactive form pages against mobile Lighthouse metrics and bundle thresholds.

A performance budget validates Next.js web vitals by comparing real Lighthouse mobile metrics like LCP, CLS, TBT, and TTFB against defined thresholds, surfacing Critical, Important, or Minor findings mapped to specific files or routes for faster fixes.

Check Next.js bundle size and chunk payloads by using next/bundle-analyzer alongside chunk scanning to flag oversized initial or lazy route payloads, ensuring your JavaScript chunks stay within defined budget limits before deployment.

Yes, this performance audit requires a successful production build running on either staging or localhost port 3000 to accurately sample server response times and validate ISR cache strategies across your key Next.js pages.

Your Next.js images and third-party scripts might hurt web vitals if image optimization patterns are missing or external scripts are blocking; the audit flags synchronous scripts and encourages next/script strategy usage to reduce load impact.

Validate ISR caching and cacheLife configuration in Next.js by checking for "use cache" directives and cacheLife() implementations on page.tsx files, ensuring your cache strategy meets performance budget criteria.