vercel-react-best-practices

To optimize React and Next.js performance during a code review, apply a priority-driven set of rules across components, pages, and data fetching. This enforces safe, consistent guidance for automated transformations and refactors bottlenecks like waterfalls and large bundle sizes.

The best way to reduce bundle size in a Next.js application is to apply targeted optimization patterns across your rendering strategies and data flows. Mapping to specific performance categories helps identify and eliminate unnecessary client-side code and waterfalls.

Server actions affect Next.js data fetching performance by shifting data flows to the server side, which can prevent client-side waterfalls. Applying optimized patterns to API routes and server actions ensures safe, consistent data fetching and rendering strategies.

Yes, you can use these React performance patterns for automated code generation. The guidelines map to specific priority categories to enforce safe, consistent transformations, allowing you to generate optimized scaffolds for components, pages, and data fetching automatically.

You should refactor client-side data fetching to improve React performance when encountering waterfalls, large bundle sizes, or inefficient SSR/CSR data flows. Applying priority-driven performance guidelines helps resolve these bottlenecks across your Next.js codebase.