---
locale: ja
translated: false
title: "The real cost of hydration in a server-first blog"
url: https://insightlog.site/ja/posts/server-components-hydration-cost
site: "InsightLog"
published: 2026-10-27T09:50:17.147Z
updated: 2026-11-20T09:50:17.148Z
author: "Daniel Okafor"
author_url: https://insightlog.site/ja/authors/daniel-okafor
type: "ガイド"
category: "Web開発"
tags: ["Next.js", "React", "SSR", "パフォーマンス"]
reading_minutes: 1
views: 404
upvotes: 29
downvotes: 2
---
## What actually ships

In a server-first app, the browser still downloads:

1. the framework runtime
2. client component code
3. the serialized RSC payload
4. props passed from server to client components

Only the first two are obvious in bundle reports. The payload and props are where regressions hide.

## Draw the boundary around interaction

Start from what must respond on the client:

- vote buttons
- reading progress
- view tracking
- theme or language menus that need local state

Everything else — article body, table of contents, cards, related posts — can stay on the server. The boundary should follow interaction, not file structure.

## The prop serialization trap

Passing a full post object into a client component serializes every field, including content. Pass the minimum: an id, a slug, a formatted count. A smaller prop surface reduces both payload size and re-render risk.

## Measure three numbers

| Metric | Where | Why |
| --- | --- | --- |
| Route JS transfer | browser network panel or build report | Shows the real shipped code |
| RSC payload size | HTML/stream size | Catches oversized props |
| Long tasks during load | performance trace | Shows hydration and script cost |

Track them per route template, not per page, so the numbers stay comparable.

## Common mistakes

1. Importing a markdown renderer into a client component.
2. Passing server data through a client wrapper that does nothing.
3. Loading analytics before the article is readable.
4. Treating a fast first paint as a fast page.

## Conclusion

Server components are a boundary tool, not a performance badge. Keep the client side small, measure the payload and make third-party scripts earn their place.
