React Server Components let you render on the server without shipping that component's JavaScript. The performance win depends on where you put the client boundary: one use client at the page level can erase most of the benefit.
Key takeaways
- Target: Keep data and static UI on the server, and ship only the interactive leaves.
- Measure field data before choosing a fix.
- Change one bottleneck at a time and re-measure on a mid-range phone.
- A fast lab score is not a substitute for real-user data.
What React Server Components measures
Inspect the client bundle and the component tree. Look for large client boundaries, unnecessary props and server data that is re-fetched on the client.
The fixes that usually move the number
- Keep
use clientat the smallest interactive leaf. - Pass serialisable data from server to client components.
- Fetch data in the server component and pass only what the client needs.
- Use Suspense and streaming for slow sections.
- Avoid importing server-only libraries into client files.
Symptom, cause and fix
| Symptom | Likely cause | What to do |
|---|---|---|
| Whole page hydrates | use client at the top | Move the boundary to the form or menu |
| Large props in the payload | Passing the entire dataset | Select the fields the client uses |
| Client refetches server data | Fetch duplicated in a client component | Pass the initial data as props |
| Build error: server-only module | A client file imports a server dependency | Move the call to a server component or route handler |
How to measure it properly
- Find client boundaries. Search for
use clientand inspect the tree below each one. - Check the payload. Look at the RSC payload and the props crossing the boundary.
- Measure hydration. Compare a server-rendered page with a client-heavy equivalent.
- Test the interaction. Confirm the client leaf still works without shipping the whole page.
- Review dependencies. Ensure server-only packages are not bundled into the client.
A practical example
// app/dashboard/page.tsx (server)
import { Filters } from "./Filters";
export default async function Dashboard() {
const data = await getDashboardData();
return (
<>
<Summary data={data.summary} />
<Filters options={data.filters} />
</>
);
}
Common mistakes
- Adding
use clientto a layout because one child needs state. - Passing functions or class instances across the server/client boundary.
- Using a client component for data that never changes.
- Fetching the same data again on the client after the server already has it.
A 30-day improvement plan
- Week 1. Collect field data and pick the worst route. Write down the baseline.
- Week 2. Fix the largest bottleneck and deploy behind a normal release.
- Week 3. Test on a mid-range phone and a throttled connection; fix regressions.
- Week 4. Compare field data, document the change and add a monitor or budget.
Field data vs lab data
| Source | What it tells you | How to use it |
|---|---|---|
| Field data | What real users experienced | The source of truth for the metric |
| Lab test | A reproducible diagnosis | Find the cause and test a fix |
| Synthetic monitoring | Availability and regressions over time | Alert on a budget breach |
| RUM segmentation | Device, country and route differences | Target the worst segment |
| Server timing | Database, cache and render time | Separate backend from frontend |
Set a performance budget
| Budget | Example starting point | Why |
|---|---|---|
| LCP | 2.5s or less at p75 | The main content must appear quickly |
| INP | 200ms or less at p75 | Interactions must feel responsive |
| CLS | 0.1 or less at p75 | Layout movement erodes trust |
| JavaScript | A route-level KB budget | Prevents bundle creep |
| Images | Responsive sizes and modern formats | The largest common payload |
| Third-party scripts | A named owner and a cap | Uncontrolled tags are a common regression |
Third-party script policy
- Every script needs an owner, a purpose and a review date.
- Load analytics and marketing tags after consent and after the main content.
- Prefer server-side events where they reduce client JavaScript.
- Test the checkout and sign-up with the full tag set enabled.
- Remove tags that no longer answer a business question.
Frequently asked questions
The target is Keep data and static UI on the server, and ship only the interactive leaves. A single fast test is not enough; use the 75th percentile of real page views and segment by mobile and desktop.
No. Start with the routes that matter to revenue or support: checkout, pricing, sign-up, the main product page and the most-read blog template. A fast homepage with a slow checkout is not a fast site.
It depends on traffic. Low-traffic sites can take weeks to accumulate enough data. Use lab tools for immediate feedback, but keep the field metric as the source of truth.
Often yes. Image dimensions, priority, bundle splits, caching and third-party scripts usually deliver more than a visual refresh. Redesign only after the measurement shows the layout itself is the bottleneck.
Sources and further reading
- Next.js server and client components (nextjs.org)
- Next.js data fetching (nextjs.org)
- React documentation (react.dev)
Related reading
Need a performance audit?
Send the URL and the metric that matters. I will identify the bottleneck, the likely fix and the cheapest way to prove it worked.
How to cite this guide: Nur Hossain Repon, “React Server Components optimization guide for Next.js and React apps”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/react-server-components-optimization-guide-for-next-js-and-react-apps.





Comments
No comments yet.