⚡ Bolt: Optimize ProjectsView image rendering and LCP loading - #149
⚡ Bolt: Optimize ProjectsView image rendering and LCP loading#149fysp11 wants to merge 1 commit into
Conversation
- Replaced incompatible Astro `<Image>` with native `<img>` inside React component - Added optimal loading attributes (`loading="lazy"`, `fetchPriority`, `decoding="async"`) - Pre-optimized images via Astro's `getImage()` on the server to maintain WebP conversions Co-authored-by: fysp11 <13081700+fysp11@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Preview deployments for fysp11.github.io ⚡️
Commit: Deployment ID: Static site name: |
1 participant
💡 What: Replaced the improperly nested Astro
<Image>component in the ReactProjectsViewcomponent with standard<img>tags, pre-optimizing those images on the server via Astro'sgetImage(). Additionally, applied eager loading &fetchPriority="high"to above-the-fold images andloading="lazy"&decoding="async"to the remainder.🎯 Why: Using Astro's
<Image>tag inside React causes bundle incompatibilities and prevents normal DOM property application (e.g. standardclass=output instead ofclassName=). Replacing it natively fixes the structure, and utilizinggetImage()on the backend preserves WebP formats and correct viewport resolutions. Proper eager/lazy indexing prevents Large Contentful Paint (LCP) blocking.📊 Impact: Faster initial LCP due to explicit
fetchPriorityandeagerloading on above-the-fold content, combined with minimized byte delivery viagetImageoptimized sizes.🔬 Measurement: Verify via
pnpm run checkpipeline, load the/projectspage locally via network devtools to observe explicitlazyboundaries, smaller asset payloads (webp), and non-blocking LCP renders.PR created automatically by Jules for task 1700553064414724324 started by @fysp11