Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
The server sends the HTML shell immediately and streams each Suspense boundary's content as its data resolves; place boundaries around independent, slower sections so the important content appears first without layout jumps.
Without streaming, the server waits for all data before sending any HTML. With streaming, it sends everything outside unresolved boundaries along with their fallbacks, then streams the completed content of each boundary later and hydrates parts as they arrive. Boundary placement trades time to first content against visual stability: wrapping each slow, independent section, such as recommendations or comments, lets the main content show early, while too many tiny boundaries produce a page that pops in piece by piece. Fallbacks should reserve roughly the final size to avoid layout shift, and critical content like the main heading should not sit behind a slow boundary.