Prioritize hero image to reduce cold-load flash#834
Merged
Conversation
👷 Deploy request for pauseai pending review.Visit the deploys page to approve it
|
RisingOrange
force-pushed
the
hero-image-fixes
branch
from
e7c32a1 to
671013e
Compare
RisingOrange
changed the title
RisingOrange
changed the title
The hero img is the largest element above the fold on /, but in prod DevTools shows it fetched at Low priority on cold loads, so it pops in late after CSS and fonts. fetchpriority=high moves it earlier in the priority queue.
RisingOrange
force-pushed
the
hero-image-fixes
branch
from
671013e to
9621f60
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The hero
<img>is the largest visible thing above the fold on/, but in prod DevTools shows it being fetched at Low priority on cold loads, which is why it visibly pops in late after CSS, fonts, and other resources settle.fetchpriority="high"moves it earlier in the priority queue.Cold-load flash before the fix
2026-05-03.00-52-47.mp4
Recorded via hard-refresh on a fast connection, so the gap is short. On a true cold visit (no cached resources, cold CDN edge, slower network) the gap is noticeably longer.
The flash won't disappear entirely —
fetchpriorityshrinks the gap, it doesn't make the image free — but on warm caches / fast networks it should be imperceptible.