serverrendered

Server-rendered refers to web content that is generated on the server and delivered to the client as complete HTML. In this approach, the server builds the page on each request, sending markup that the browser can render immediately, often followed by client-side JavaScript that hydrates the page to enable interactivity. This contrasts with client-side rendering, where the browser runs code to render the UI from data fetched after the initial load.

There are variations of server rendering, including true server-side rendering on every request and hybrid patterns where the initial HTML is server-generated and later enhanced by JavaScript. Some systems also employ streaming or partial rendering to send portions of the page as they become ready.

Advantages of server rendering include better search engine optimization, reliable content delivery without heavy client-side processing, and faster perceived first contentful paint on slower devices. It is well suited for content-heavy sites, marketing pages, and pages that must be accessible with JavaScript disabled or with limited devices. Disadvantages include higher server load and latency compared with purely client-side approaches, the need for robust server infrastructure, and potential complexity around caching, data freshness, and hydration errors when the client script and server markup diverge.

Common technologies and frameworks used for server rendering include Next.js and Nuxt.js for React and Vue ecosystems, as well as traditional server-rendered templates in Ruby on Rails, Django, and PHP. Performance often relies on caching strategies, edge rendering, and, in some cases, streaming SSR to improve responsiveness.