⚡ Bolt: [성능 최적화] 초기 SVG 이미지의 비동기 디코딩 제거로 LCP 개선 - #146
Conversation
|
👋 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. |
|
Warning Review limit reached
Next review available in: 2 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Comment |
|
Closing as superseded by #141. Both branches remove |
Understood. Acknowledging that this work is now obsolete and stopping work on this task. |
💡 What:
화면 상단(Above-the-fold)에 위치한 핵심 SVG 이미지(사이트 로고
assets/context-wisdom-lab-avatar.svg및 Hero 그래픽assets/context-thread-map.svg)에서decoding="async"속성을 제거했습니다. 아울러 기존에 모든 이미지에 대해decoding="async"를 확인하던tests/test_styles.py테스트 코드가 지연 로딩(loading="lazy")되는 이미지에만 이를 기대하도록 수정했습니다.🎯 Why:
decoding="async"는 브라우저에게 이미지 디코딩 작업을 별도의 스레드로 미루도록 지시하여 메인 스레드 블로킹을 방지합니다. 그러나 LCP(Largest Contentful Paint)에 영향을 주는 중요 초기 화면 이미지에 이를 적용하면 렌더링이 의도적으로 지연되어 LCP 성능이 오히려 하락하는 병목(bottleneck) 현상을 초래할 수 있습니다.📊 Impact:
화면 상단 주요 SVG 이미지들이 동기적으로 디코딩됨으로써 브라우저가 첫 렌더링(First Contentful Paint) 시점에 이미지를 함께 그려내어 LCP 시간을 단축시킵니다. (오프스크린 이미지는 여전히 지연 디코딩되므로 메인 스레드 성능은 유지됩니다.)
🔬 Measurement:
브라우저 DevTools의 Lighthouse 패널이나 Performance 탭을 활용해 캐시를 비운 상태에서 재로드 시 LCP(Largest Contentful Paint) 타이밍이 기존보다 단축되는지 확인합니다. 또한
pytest tests/test_styles.py를 실행하여 테스트 통과를 검증할 수 있습니다.PR created automatically by Jules for task 12858554996407043357 started by @seonghobae