vercel-react-best-practices

To fix slow React and Next.js performance, restructure async dependencies for parallelization and use Suspense streaming. This eliminates server/client waterfalls by analyzing data fetching patterns and applying safer loading strategies to produce faster code changes.

The best way to reduce bundle size is using safer import strategies, dynamic conditional loading, and after-hydration loading for non-critical third-party code. This minimizes client payload size and improves load times without breaking rendering.

Optimize React Server Components prop serialization by analyzing RSC boundary prop payloads and applying rendering-performance rules. This reduces serialization overhead and avoids shared module state hazards during refactoring.

Unnecessary re-renders and UI stalls happen due to inefficient rendering patterns and unoptimized React rendering behaviors. Applying targeted re-render rules and analyzing component structures resolves these runtime efficiency issues.

Yes, you can refactor Server Actions and Route Handlers in Next.js. The process analyzes data fetching, loading strategies, and async dependency structures to produce safer and faster code changes.

You need to optimize data fetching and loading strategies when diagnosing performance regressions like slow TTI/LCP or excessive network round-trips. Restructuring these patterns removes waterfalls and improves rendering efficiency.