check-perf

Auditing Next.js performance involves analyzing production builds to measure route and chunk sizes, flagging burdensome routes. This process identifies large bundles and highlights optimization opportunities across your application.

Detecting unnecessary use client directives requires scanning your Next.js project for client-side code patterns. A client-audit highlights components that push server-side logic to the client unnecessarily, helping you optimize server and client boundaries.

Identifying heavy imports and missing lazy loading involves detecting large or rarely used imports to suggest tree-shaking, and identifying components loaded too early to recommend dynamic imports and Suspense boundaries for optimized loading.

Yes, Next.js performance audits include image optimization checks that flag non-optimized images and missing next/image usage. This ensures your application handles media efficiently and follows framework-specific best practices.

Yes, you can apply this bundle analysis to typical Next.js apps with routes and pages. It is designed to identify routes with large bundles, unnecessary client code, and missed lazy loading across both server and client code.

Suspense boundary verification is needed to ensure components are not loaded too early. By verifying these boundaries, you can implement dynamic imports correctly, preventing performance bottlenecks and improving overall page load times.