Where pages are produced.
WHAT THE OPTIONS ARE
Rendered on the server for each request Generated in advance as static files Rendered in the browser Combinations
WHAT SERVER RENDERING PROVIDES
Content present in the initial response Better performance on slow devices Reliable indexing by search engines
WHAT STATIC GENERATION PROVIDES
The same, with no server work per request.
WHAT IT SUITS
Content that changes infrequently.
WHAT BROWSER RENDERING PROVIDES
Rich interactivity after loading.
WHAT IT COSTS
Nothing visible until scripts load and execute Poorer performance on modest devices Additional work for indexing
WHAT HYDRATION IS
Attaching behaviour to server-rendered markup in the browser.
WHAT TO CHOOSE
Static where possible Server rendering for dynamic content Browser rendering for genuinely application-like interfaces
WHAT MATTERS MOST HERE
That something useful appears quickly on a modest device and a slow connection.
WHAT TO TEST
First meaningful content, on a real phone.
