Resources · glossary
SSR, SSG and CSR (rendering methods)
Three answers to the question of where a page is built: on the server on every visit (SSR), in advance as a ready file (SSG), or in the user's browser (CSR). The choice shows in speed and in whether the search engine has anything to index.
- server-side rendering
- static site generation
- client-side rendering
- rendering strategies
- 01
Why this is not just a technical topic
Because it affects two things that cost money: how quickly content appears on screen, and whether Google sees it without running code. With CSR both answers can be unfavourable.
- 02
Which one when
Content that rarely changes should be built in advance (SSG). Content that depends on the user, such as a basket, an account panel or search results, has to be built on the server (SSR). The browser (CSR) is left with what requires a login anyway and what the search engine has no business seeing.
- 03
What it means for search engines
Google can run a page's code, but it does so in a second pass and not always. The content you care about should be in the server's response, not drawn in after it.
- 04
How to check what you have
The simplest way is a speed test: a page that shows an empty space for a long time before the content appears is usually assembled in the browser. Our test runs this check on a public address in under a minute.
Related terms
- Core Web VitalsThree metrics Google uses to measure how using a page feels: how fast the main content appears, how fast the page responds and whether the layout jumps under your finger.
- JAMstackA way of building websites in which pages are generated in advance as ready files, and data comes from external services through APIs. The server does not assemble the page on every visit, so it is faster and cheaper.
15 minutes. No sales pitch.
A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.