Prerender preloads the header logo instead of each page's hero image #233
Labels
No Label
P0
P1
P2
P3
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
phase-7
phase-8
release-blocker
security
seo
ui
ux
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Queue-North-Website#233
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seen at
a25077d(v0.9.5).What is true now.
scripts/prerender.js:68-81picks the hero preload as the first<img loading="eager">, which is the header logo (src/components/layout/Header.jsx:66), and drops React's own preload for the real hero image. Every built page preloads/logo.pngwithfetchpriority="high". The comment there says the opposite.What it costs. The largest image on every page starts loading late; Largest Contentful Paint is a ranking signal.
What to do. Select the image carrying
fetchpriority="high", which is the hero. Correct the comment.Trap. React writes the attribute as
fetchPriority, camelCase. A case-sensitive match silently removes every hero preload.Verify: no built page preloads
/logo.png, anddist/services/contact-center/index.htmlpreloads/assets/modern-call-center.webp.Fixed in
28b07ab. scripts/prerender.js now keys the hero preload on the image React marked with a high fetch priority, matched case-insensitively because React writes fetchPriority camelCase in HTML. Verified against a build: / and /services/unified-communications preload /assets/hero-tech.webp, /services/contact-center and /industries/healthcare preload /assets/modern-call-center.webp, and grep finds no page preloading /logo.png. The stale comment claiming the eager image is the hero was corrected too.