Skip to content
BENIBIX Learn

Server-Side Rendering vs Client-Side Rendering

With server rendering, the server builds the page and sends it ready to read. With client rendering, the browser gets code and builds the page itself. That makes the first view slower.

Development🌐 Web Development

Server-Side Rendering (SSR)

The server builds the full page for each visit. It arrives ready to show.

Server-side rendering means the server builds the full page for each visit. It sends HTML that is ready to show. The user sees content at once, before any JavaScript runs. Search engines can read the page with ease too. The cost is more work on the server each time. Many new frameworks mix it with browser code, in a step called hydration.

Example
Emma's news site renders each article on the server. Readers on slow phones see the text in under a second.
Why it matters
SSR shows content fast and is easy for search engines. That matters for shops and news.
Full entry
Development🌐 Web Development

Client-Side Rendering (CSR)

The browser builds the page with JavaScript. It starts once the code arrives.

Client-side rendering means the browser builds the page with JavaScript. The server sends a nearly empty HTML file plus the code. The code then runs in the browser, fetches data and draws the page. It keeps the server simple and makes later clicks fast. But the user sees a blank screen until the code has loaded and run.

Example
Jack's dashboard sends a tiny HTML file and a 400 KB script. On a slow phone, the screen stays blank for 3 seconds before the charts appear.
Why it matters
It decides how fast a page first shows. On slow phones, CSR can feel very slow.
Full entry

In one line

Server-Side Rendering (SSR)
The server builds the full page for each visit. It arrives ready to show.
Client-Side Rendering (CSR)
The browser builds the page with JavaScript. It starts once the code arrives.