⚡ Bolt: Optimize project images and loading priorities - #155
Conversation
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: |
💡 What:
astro:assets<Image />component with a standard<img>tag inProjectsView.tsx.projects/index.astrousingimport.meta.globandgetImage(), passing only the optimized URL string to React.🎯 Why:
Astro's
<Image />component is not fully supported inside React UI components for dynamic processing. By moving optimization to the Astro server layer, we retain WebP generation and resizing. Adding proper above/below-the-fold logic prevents lazy-loading LCP images while deferring offscreen assets.📊 Impact:
fetchPriority="high",loading="eager").loading="lazy",decoding="async").🔬 Measurement:
Run
pnpm run checkto verify build succeeds. Check the network tab on/projectsto see first 4 images load immediately while remaining load on scroll.PR created automatically by Jules for task 11318335354887401318 started by @fysp11