Comparison
Server-side renderingvsStatic site generation
Server-side rendering
the HTML arrives with the content already in it, and the page is readable before any script runs.
Running the component code on the server for each request and sending finished HTML. It gets content on screen sooner and gives crawlers something to read, at the cost of a server that must render on every request and a time-to-first-byte that now includes your data fetching. The rendered HTML is inert until hydration, so 'visible' and 'usable' become two different moments you have to measure separately.
Full entry →Static site generation
every page was rendered once at build time and the server is just handing out files.
Rendering every page during the build and serving the results as static files from a CDN. It is the fastest and cheapest option and the one with the fewest moving parts at runtime. It breaks down when the content changes often or depends on who is asking, because the only way to update a page is to rebuild it, and build time grows with the number of pages.
Full entry →