vercel-react-best-practices

To identify React performance bottlenecks, evaluate server and client data fetching, rendering optimizations, and bundle-size reductions across pages, components, routes, and API handlers to pinpoint runtime latency and re-render issues.

The best way to reduce bundle size involves analyzing your pages and components to apply safe refactoring with concrete improvements, eliminating unnecessary code waterfalls while preserving existing behavior and enforcing validation.

Optimizing server-side data fetching requires enforcing safe refactoring with validation and testable steps, eliminating waterfalls across pages, routes, and API handlers while preserving existing behavior in your Next.js project.

Yes, this optimization approach covers both client-side data fetching and server-side performance, providing practical examples and trade-offs for common patterns like pages, components, and server actions in Next.js.

The limitation of refactoring for re-render optimization is that changes must preserve existing behavior through validation and testable steps, ensuring safe refactoring without introducing runtime latency or breaking component functionality.

Yes, you can generate a concrete refactor plan for your React and Next.js project by applying comprehensive rules across 8 categories, including rendering performance, bundle size, and advanced patterns, to guide code review and refactoring.