Questions
18 of 27
1What are client components?
2How to implement client rendering in next js?
3Describe how client components are rendered.
4How to decide what part should be rendered on the server and what on the client?
5Combining client and server components
6How to render a server component in the client component?
7Discuss best approaches with client components.
8Does using 'use client' ensure that the component only renders on the client?
9Explain the full lifecycle of a CSR page in Next.js — from initial HTML delivery to interactive UI.
10What is the difference between useEffect data fetching and React Query / SWR in a CSR context?
11When would you choose CSR over SSR or SSG in a production Next.js app? Give real-world examples.
12How does React's concurrent rendering model affect CSR behaviour in Next.js 13+?
13How do you handle deeply nested Client Components without causing unnecessary re-renders?
14Explain the concept of "client component boundaries" — how do they affect the component tree?
15How would you implement optimistic UI updates in a CSR-heavy Next.js application?
16What are the challenges of using Context API at scale in a CSR and SSR? How do you solve them?
17How does next/dynamic work? How is it different from React's lazy() and Suspense?
18What is the "flash of unstyled/unloaded content" problem in CSR, and how do you prevent it?
19How do you prefetch data for CSR pages in Next.js to reduce perceived latency?
20How do useMemo and useCallback help performance in CSR components? When are they overkill?
21How do you implement skeleton screens or loading states for CSR data fetching?
22Compare SWR vs React Query vs useEffect for client-side data fetching — when do you use each?
23How do you implement infinite scrolling or pagination purely on the client side in Next.js?
24How do you handle race conditions in CSR data fetching with useEffect?
25What is the difference between client-side fetch and server actions in Next.js App Router?
26How do you cancel in-flight API requests when a component unmounts in CSR?
27How would you handle real-time data (WebSockets / SSE) in a Next.js CSR component?
nextjsnextjs
Basics
Project Structure
Runtime
Compiler
SSG
SSR
CSR
Routing
Route Handlers
Route Groups
Dynamic Routes
Parallel Routes
Intercepting Routes
Middleware
Server Actions
APIS
Data Fetching
Caching
Clients
Optimisation
i18n
Security
Architecture
Deployment
Accessibility
18 / 27

What is the "flash of unstyled/unloaded content" problem in CSR, and how do you prevent it?

Flash of Unstyled/Unloaded Content (FOUC) in CSR occurs when raw HTML or loading states briefly appear before JavaScript loads and hydrates, which can be prevented through SSR/SSG, skeleton screens, CSS optimization, and critical CSS inlining

Flash of Unstyled Content (FOUC) and Flash of Unloaded Content are visual glitches in Client-Side Rendering where users briefly see unstyled HTML, loading spinners, or incomplete layouts before React hydrates and replaces them with the final UI . This happens because CSR delivers a minimal HTML shell first, then downloads JavaScript, executes it, and finally renders content—leaving a gap where the page appears broken or empty . In Next.js, this is less severe than pure CSR because of automatic server rendering, but can still occur with client-only components, dynamic imports, or slow network conditions .

Types of Flash Problems
  1. 1

    Flash of Unstyled Content (FOUC): Raw HTML appears with browser default styling before CSS loads, causing jarring visual shifts .

  2. 2

    Flash of Unloaded Content (FOULC): Loading spinners or placeholders appear while data fetches, then suddenly replace with content .

  3. 3

    Flash of Incorrect Layout: Content loads but layout shifts dramatically as images or dynamic content populate .

Unlike pure CSR apps, Next.js automatically pre-renders pages on the server, delivering complete HTML with styles already applied. This eliminates FOUC for most pages. However, problems arise when using client-only components with ssr: false, dynamic imports without proper placeholders, or data fetching that shows loading states before content . These patterns create moments where the user sees loading UI instead of content.

Problem: Client-Only Component with FOUC
Solution 1: Provide Matching Placeholders

FOUC specifically refers to unstyled HTML appearing before CSS loads. In Next.js, this can happen with global CSS imports or CSS-in-JS libraries. Prevent it by inlining critical CSS for above-the-fold content . Next.js automatically inlines critical CSS for each page, but you can optimize further by using the @next/plugin-google-fonts or manually extracting critical CSS with tools like critters.

Solution 3: Optimize Dynamic Imports

The most effective prevention is using SSR/SSG for critical content. When pages are server-rendered, users receive complete HTML immediately—no FOUC . For interactive elements that must be client-only, ensure they have skeleton screens that match the final content dimensions and layout . The key is making the loading state visually similar to the loaded state so transitions feel smooth rather than flashy.

Best Practices Summary
  1. 1

    Prefer SSR/SSG over client-only rendering for content users should see immediately .

  2. 2

    Use loading skeletons that match the dimensions and layout of final components .

  3. 3

    Avoid ssr: false for above-the-fold content—use it only for heavy, non-critical components .

  4. 4

    Implement CSS transitions for opacity or height changes to smooth content appearance .

  5. 5

    Use the Web Vitals metrics to monitor Layout Shift (CLS) and catch FOUC issues .