SSR (Server-Side Rendering)
SSR means that a page’s HTML is generated on the server separately for each request, rather than later in the user’s browser.
It contrasts with the classic SPA (Single Page Application) approach, where the browser receives almost empty HTML and JavaScript only then renders the content. SSR sends ready-made HTML straight away - the content is visible (and readable for search engines and AI crawlers) before JavaScript has time to download and run.
The advantage is twofold: faster LCP (the content is ready sooner) and better SEO/AI readability - the crawler does not have to wait for JavaScript to execute to see the page’s actual content. The drawback is higher server load, because HTML is generated again for every request (unlike SSG, which is generated once in advance).
Next.js lets you combine both approaches at the individual-page level - static generation where content does not change with every request, and server-side rendering where it does. This exact combination is behind this website’s performance and the redesign of bazarfoto.cz.
Related service
Next.js development →