Deferred data with streaming in Remix - Performance & Optimization

Performance: Deferred data with streaming

HIGH IMPACT

This affects how quickly the main content appears and how smoothly the page responds while loading additional data.

Loading a page with some data that can be delayed

Remix

import { defer, Await, useLoaderData } from "@remix-run/react";
import { Suspense } from "react";

export async function loader() {
  const mainData = await fetchMainData();
  const slowDataPromise = fetchSlowData();
  return defer({ mainData, slowData: slowDataPromise });
}

export default function Page() {
  const { mainData, slowData } = useLoaderData();
  return <>
    <MainContent data={mainData} />
    <Suspense fallback={<LoadingSpinner />}>
      <Await resolve={slowData}>
        {(data) => <SlowContent data={data} />}
      </Await>
    </Suspense>
  </>;
}

Main content renders immediately; slow data loads asynchronously and streams in, improving perceived speed.

📈 Performance GainReduces LCP by showing main content early; slow data loads without blocking rendering.

Loading a page with some data that can be delayed

Remix

export async function loader() {
  const mainData = await fetchMainData();
  const slowData = await fetchSlowData();
  return { mainData, slowData };
}

export default function Page() {
  const { mainData, slowData } = useLoaderData();
  return <>
    <MainContent data={mainData} />
    <SlowContent data={slowData} />
  </>;
}

Waiting for all data before rendering blocks the page from showing anything until slow data arrives.

📉 Performance CostBlocks rendering for the full slow data fetch time, increasing LCP significantly.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking full data load	Single batch DOM update after all data arrives	1 reflow after all data loads	High paint cost due to delayed content	[X] Bad
Deferred streaming with Suspense	Initial DOM update with main content, incremental update for slow data	1 reflow for main content, 1 reflow for streamed data	Lower paint cost, faster first meaningful paint	[OK] Good

Rendering Pipeline

Deferred streaming splits data loading so the browser can paint main content early, then update with streamed data later.

→Data Fetching

→HTML Streaming

→Paint

→Composite

⚠️ BottleneckData Fetching and initial HTML streaming

Core Web Vital Affected

LCP

This affects how quickly the main content appears and how smoothly the page responds while loading additional data.

Optimization Tips

1Always send critical data first to reduce blocking time.

2Use React Suspense and Remix defer to stream slow data.

3Avoid waiting for all data before rendering to improve LCP.

Performance Quiz - 3 Questions

How does deferred data with streaming improve Largest Contentful Paint (LCP)?

A By loading all data before rendering anything

B By delaying all data until user interaction

C By showing main content immediately and loading slow data later

D By removing slow data completely

DevTools: Performance

How to check: Record a page load, look for the time to first meaningful paint and check if main content appears before slow data loads.

What to look for: Shorter gap between navigation start and main content paint indicates good deferred streaming.

Practice

1. What is the main purpose of using defer() in Remix loaders?

easy

A. To cache data permanently on the server

B. To block rendering until all data is loaded

C. To load some data parts asynchronously and improve page speed

D. To preload all images before rendering

Solution

1. Step 1: Understand what defer() does in Remix loaders

   defer() allows parts of the data to load asynchronously, so the page can start rendering before all data arrives.

2. Step 2: Compare options with this behavior

   To load some data parts asynchronously and improve page speed correctly describes asynchronous partial loading to improve speed. Options A, B, and D describe blocking, caching, or preloading images, which are not the purpose of defer().

3. Final Answer:

   To load some data parts asynchronously and improve page speed -> Option C

4. Quick Check:

   defer() = async partial loading [OK]

Hint: Remember defer() means 'delay some data' to speed up page [OK]

Common Mistakes:

• Thinking defer() blocks rendering until all data loads
• Confusing defer() with caching or preloading images
• Assuming defer() loads everything synchronously

2. Which of the following is the correct way to use defer() in a Remix loader?

easy

A. return defer({ user: fetchUser })

B. return defer(fetchUser())

C. return deferUser(fetchUser())

D. return defer({ user: fetchUser() })

Solution

1. Step 1: Check the syntax of defer() usage

   defer() expects an object with keys mapping to promises or data. So defer({ user: fetchUser() }) is correct because it passes an object with a promise.

2. Step 2: Analyze other options

   return defer(fetchUser()) passes a promise directly, not an object. return deferUser(fetchUser()) uses a non-existent function deferUser. return defer({ user: fetchUser }) passes the function fetchUser without calling it, so it passes a function, not a promise.

3. Final Answer:

   return defer({ user: fetchUser() }) -> Option D

4. Quick Check:

   defer() needs an object with promises [OK]

Hint: defer() always wraps an object with promises [OK]

Common Mistakes:

• Passing a promise directly instead of inside an object
• Passing a function instead of calling it
• Using non-existent functions like deferUser

3. Given this loader code:

export async function loader() {
  return defer({
    user: fetchUser(),
    posts: fetchPosts()
  });
}

And this component snippet:

<Suspense fallback="<p>Loading posts...</p>">
  <Await resolve={data.posts}>
    {(posts) => <PostList posts={posts} />}
  </Await>
</Suspense>

What will the user see first when the page loads?

medium

A. The user data immediately, and a loading message for posts

B. Nothing until both user and posts load

C. Only the posts list immediately

D. An error because Suspense is missing for user

Solution

1. Step 1: Understand deferred data loading

   The loader defers both user and posts. The component uses Suspense and Await only for posts, so posts will show a loading fallback until ready.

2. Step 2: Predict what renders first

   User data is not wrapped in Suspense here, so it will render immediately if available. Posts will show the fallback message until loaded.

3. Final Answer:

   The user data immediately, and a loading message for posts -> Option A

4. Quick Check:

   User shows immediately; posts show fallback [OK]

Hint: Suspense controls what shows loading fallback [OK]

Common Mistakes:

• Assuming all deferred data waits for Suspense
• Thinking nothing shows until all data loads
• Confusing which data is wrapped in Await

4. This loader code causes an error:

export async function loader() {
  const user = fetchUser();
  return defer(user);
}

What is the problem and how to fix it?

medium

A. defer() expects an object; fix by returning defer({ user })

B. fetchUser() must be awaited before defer()

C. defer() cannot be used with async functions

D. No problem; code works fine

Solution

1. Step 1: Identify defer() argument requirements

   defer() requires an object mapping keys to promises or data, not a single promise.

2. Step 2: Fix the code

   Wrap the promise in an object: defer({ user }) to fix the error.

3. Final Answer:

   defer() expects an object; fix by returning defer({ user }) -> Option A

4. Quick Check:

   defer() needs an object argument [OK]

Hint: Always pass an object to defer(), never a single promise [OK]

Common Mistakes:

• Passing a single promise directly to defer()
• Awaiting fetchUser() before defer() unnecessarily
• Thinking defer() can't be used with async functions

5. You want to show a user profile page where the user info loads immediately, but the user's posts load later with a loading message. Which is the best way to implement this using deferred data and streaming in Remix?

hard

A. Await both fetchUser() and fetchPosts() in loader, then render all data together

B. Use defer({ user: fetchUser(), posts: fetchPosts() }) in loader, render user directly, wrap posts in Suspense and Await

C. Use defer(fetchUser()) and defer(fetchPosts()) separately in loader

D. Render user and posts without Suspense or Await, rely on browser streaming

Solution

1. Step 1: Understand deferred data usage for partial loading

   Using defer() with an object containing both user and posts lets you load them independently.

2. Step 2: Use Suspense and Await to show loading fallback only for posts

   Render user data directly since it loads fast, and wrap posts in Suspense and Await to show a loading message until posts arrive.

3. Final Answer:

   Use defer({ user: fetchUser(), posts: fetchPosts() }) in loader, render user directly, wrap posts in Suspense and Await -> Option B

4. Quick Check:

   defer + Suspense/Await for partial loading [OK]

Hint: Wrap only slow data in Suspense/Await, defer all in loader [OK]

Common Mistakes:

• Awaiting all data in loader, losing streaming benefits
• Using defer() incorrectly with separate calls
• Not using Suspense/Await for deferred parts