Architecture for Frontend Performances
Performance architecture is choosing how and where pages are rendered. Options include client-side rendering, server-side rendering, static generation, incremental regeneration, streaming and islands. Each shifts cost between the server, the CDN and the user's device, and changes metrics like LCP and Time to First Byte.
Stage: Production · Part of the Frontend Performance roadmap · Last reviewed 19 November 2026
What to learn in Architecture
- Compare CSR, SSR, SSG and ISR for time to first byte and interactivity
- Pick a rendering strategy for a given page type
- Stream HTML so the shell appears before slow data arrives
- Explain how partial hydration and islands reduce shipped JavaScript
- Use edge caching to serve dynamic pages faster
Architecture interview questions
Why can client-side rendering give a poor LCP?
The browser must download, parse and run JavaScript, then fetch data and build the DOM before meaningful content appears. Server rendering or static HTML puts content in the first response, so the LCP element can be painted much sooner.
What problem do islands solve?
Islands architecture ships HTML for the whole page but hydrates only the interactive components. Static parts like text and images need no JavaScript, so far less code is downloaded and executed, improving load and interaction metrics.
Where Architecture fits in the Frontend Performance roadmap
Architecture belongs to the Production stage (advanced level). Keep it fast.
Other units in this stage
Back to the full Frontend Performance roadmap