# Server-side rendering

Concept · [Technical basics](https://ecosystem.samcarlton.com/technical)

Also called: SSR, server rendered, server-side rendered, server rendering

Building a web page's [HTML](https://ecosystem.samcarlton.com/html) on the [server](https://ecosystem.samcarlton.com/server) before sending it, instead of in the visitor's [browser](https://ecosystem.samcarlton.com/web-browser). Pages tend to show up faster and are easier for search engines to read.

**For example:** A store renders each product page on the [server](https://ecosystem.samcarlton.com/server), so it appears quickly even on a slow phone.

## Connects to (5)

- [Front end](https://ecosystem.samcarlton.com/front-end): The part of an app or website that people see and tap, running in their browser or on their phone.
- [Back end](https://ecosystem.samcarlton.com/back-end): The part of an app that runs out of sight on a server.
- [Static site](https://ecosystem.samcarlton.com/static-site): A website made of fixed pages that look the same for every visitor.
- [Search engine optimization](https://ecosystem.samcarlton.com/search-engine-optimization): Making a website easier for search engines to understand and more likely to show up when people search for what you offer.
- [Next.js](https://ecosystem.samcarlton.com/next-js): A framework built on React for making full websites and web apps, including pages rendered on the server.

Map view: https://ecosystem.samcarlton.com/server-side-rendering
