Server-side rendering: Meaning, examples and limitations
Server-side rendering, or SSR, creates a page’s HTML on the server before sending it to the browser. The response can already contain meaningful content, while optional client-side code adds interactive behavior afterward.
At a glance
- SSR can include the main text in the initial response.
- It may still ship substantial JavaScript for hydration.
- Request-time rendering has operational and caching costs.
On this page

What work happens on the server?
The server combines a template, application logic and data into HTML. A browser can begin reading that response without first assembling all the content from a client-side data request. This is different from client-side rendering, where scripts build the main content in the browser.
SSR describes where rendering happens, not a guarantee about the page's total download size or speed. A server-rendered page can still send a large script bundle. Rendering reference
Example: a public reference article
Suppose the response for a definition contains its heading, explanation, links and image. Readers can access those elements immediately as HTML is processed. JavaScript may then activate optional controls. If every paragraph waits for a later browser API request, the main content is not being delivered in that initial HTML.
Verify both the response and the network activity. A screenshot of the finished page cannot tell you how much work was required to reach it.
Is SSR the same as static generation?
No. Static generation prepares HTML ahead of visits; SSR commonly renders when a request arrives. Caches and regeneration strategies can combine the two ideas, so examine the actual route behavior rather than the framework's label.
Request-time rendering may call databases or other services. A page cache can reduce repeated work for safe public responses, but personalized pages need deliberate isolation. Faster delivery must not mix one visitor's account data with another's.
What should be measured?
Check time to first byte, transfer size and what runs in the browser. Hydration can add CPU work even when the text was server-rendered. Test slower phones and failed dependencies as well as a fast desktop. SSR can improve content availability, but it does not automatically mean zero JavaScript, zero server cost or guaranteed search inclusion.