Static Rendering

Based on our discussion on SSR, we know that a high request processing time on the server negatively affects the TTFB. Similarly, with CSR, a large JavaScript bundle can be detrimental to the FCP, LCP and TTI of the application due to the time taken to download and process the script.

Static rendering or static generation (SSG) attempts to resolve these issues by delivering pre-rendered HTML content to the client that was generated when the site was built.

When to Use

• Use this for static content like About pages, blog posts, and product listings that don't change per-request
• This is helpful when you want the fastest possible TTFB via CDN-served static HTML

When NOT to Use

• For highly dynamic, personalized content that changes per request (e.g., user dashboards, real-time feeds)
• When the dataset is so large that build times become impractical without ISR
• For pages requiring authentication-gated content that can't be pre-rendered at build time

Instructions