Skip to content

docs: outlining and lcp - #96942

Draft
icyJoseph wants to merge 3 commits into
canaryfrom
docs-streaming-lcp
Draft

docs: outlining and lcp#96942
icyJoseph wants to merge 3 commits into
canaryfrom
docs-streaming-lcp

Conversation

@icyJoseph

Copy link
Copy Markdown
Member

LCP can be affected if the LCP element is sitting within a Suspense boundary, even if its nothing but static content, if the static content is "too large".

Apps should prefer, as long as possible, to not have a Suspense boundary around the LCP element.

Waiting for a large boundary’s HTML to arrive during streaming server rendering. Sending HTML takes time, so a boundary with enough content activates even when nothing in it suspends. React reveals the content as the HTML arrives.

The LCP element stops depending on initial server response time and
starts depending on the server's render work plus the browser running
the streamed swap script. Add a rule of thumb about not adding
boundaries you don't need.
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Stats skipped

Commit: 5c5fc19
View workflow run

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Tests Passed

Commit: 5c5fc19

Split the comma-heavy sentence, drop mid-sentence colons and the bare
'this' subject, and flip the non-image bullet to positive phrasing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants