What is SSR Per Request?
Fresh HTML rendered on the server for every request, used for personalized or frequently changing pages. Server rendering guarantees complete markup on first paint but costs compute per visit, so reserve it for dynamic routes.
Related terms
Prerendering (Static)
Build-time HTML generation: pages render once during the build and ship as static files. This BYOB site defaults to prerendered routes with explicit opt-outs, so content loads fast and crawlers see complete markup.
CSR Shell
A minimal HTML shell that renders content in the browser after JavaScript loads. Client rendering suits authenticated dashboards behind login, where SEO matters less and interactivity starts only after scripts execute.
Server-Side Rendering
Rendering full HTML on the server per request so crawlers and users receive complete content immediately. The SEO-safe default for content pages in frameworks like SvelteKit and Next.js.
Hydration Cost
The JavaScript work that turns server-rendered HTML into an interactive app. Hydration replays component logic in the browser, so oversized bundles delay input readiness even when paint looks instant.
SvelteKit adapter-static
A SvelteKit build target that emits a fully static site with no server runtime. Fully static output fits documentation and marketing pages, but any route needing server logic must switch back to a server adapter.
Immutable Hashed Assets
Static files with content hashes in their filenames, emitted under the immutable build output. When code changes the hash changes, so browsers safely cache each version forever without risking stale JavaScript or styles.