{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigqwslyfknlxkxyacyvlnz36reaxuhbc454yuif5wwq6k6ld6b4cy",
    "uri": "at://did:plc:5sgu76a53rz3n6unbykmovqy/app.bsky.feed.post/3mlpoisvohjy2"
  },
  "description": "Server-Side Rendering (SSR) is the practice of rendering a page's HTML on the server in response to a request, then sending the fully formed markup to the browser, optionally followed by JavaScript that hydrates the page for interactivity. SSR contrasts with Client-Side Rendering (CSR), where the server returns a near-empty HTML shell and the browser builds the UI from JavaScript.\n\n\nWhy SSR matters\n\n * Faster first paint. Users see content before JavaScript downloads and parses.\n * SEO. Crawlers",
  "path": "/engineering-glossary/ssr-server-side-rendering/",
  "publishedAt": "2026-05-14T00:00:00.000Z",
  "site": "https://sahilkapoor.com",
  "tags": [
    "CSR",
    "Next.js",
    "Nuxt",
    "Astro",
    "React"
  ],
  "textContent": "**Server-Side Rendering (SSR)** is the practice of rendering a page's HTML on the server in response to a request, then sending the fully formed markup to the browser, optionally followed by JavaScript that hydrates the page for interactivity. SSR contrasts with Client-Side Rendering (CSR), where the server returns a near-empty HTML shell and the browser builds the UI from JavaScript.\n\n## Why SSR matters\n\n  * **Faster first paint.** Users see content before JavaScript downloads and parses.\n  * **SEO.** Crawlers see real content immediately; helpful even though modern Googlebot also runs JS.\n  * **Lower client cost.** Less work for the user's device, especially on low-end hardware.\n  * **Personalised content.** Per-request data can be embedded directly in the initial HTML.\n\n\n\n## Related rendering modes\n\n  * **SSG (Static Site Generation).** Render at build time; serve from CDN. Cheapest at scale; freshest content updates require rebuild.\n  * **ISR (Incremental Static Regeneration).** Static pages refreshed in the background after a TTL; combines SSG cost with SSR-like freshness.\n  * **Streaming SSR.** Server flushes HTML in chunks as parts of the page resolve; React Suspense, Astro, Qwik.\n  * **Edge rendering.** SSR at the edge for low global latency (Vercel Edge, Cloudflare Workers, AWS Lambda@Edge).\n\n\n\n## Hydration\n\nAfter SSR delivers HTML, the browser downloads the framework and re-runs components against the server-rendered DOM to attach event listeners and state. Frameworks like Qwik and Astro reduce this cost via resumable execution or no-hydration islands.\n\n🔗\n\n**Related Terms**\nCSR, Next.js, Nuxt, Astro, React.",
  "title": "Server-Side Rendering (SSR)",
  "updatedAt": "2026-05-13T19:14:02.072Z"
}