⚡ Bolt: LCP 요소에서 decoding="async" 제거를 통한 초기 렌더링 최적화

[seonghobae]

💡 What

index.html의 주요 LCP(Largest Contentful Paint) 요소인 above-the-fold 이미지(헤더 아바타와 히어로 섹션 아트워크)에서 decoding="async" 속성을 제거했습니다. 이와 관련된 tests/test_styles.py 테스트 코드를 수정하여, loading="lazy"인 이미지만 decoding="async"를 강제하도록 변경했습니다.

🎯 Why

decoding="async" 속성은 이미지를 별도의 스레드에서 디코딩하여 메인 스레드 차단을 방지하는 데 유용하지만, 초기 화면에 렌더링되어야 하는 LCP 핵심 이미지에 적용될 경우 디코딩이 완료될 때까지 표시가 지연되어 체감 렌더링 성능(LCP)이 저하되는 원인이 됩니다.

📊 Impact

사용자 첫 화면(above-the-fold)에 표시되는 핵심 시각 요소들의 렌더링 지연을 방지하여 LCP를 개선합니다. 백그라운드 작업으로 미뤄지는 렌더링 오버헤드를 줄여 사용자가 이미지를 더 빨리 인식할 수 있습니다.

🔬 Measurement

브라우저 DevTools의 Performance 탭이나 Lighthouse를 통해 메인 페이지의 LCP 지표(타이밍)가 단축되었는지 확인합니다.

---

PR created automatically by Jules for task 15205974802706399005 started by @seonghobae

[google-labs-jules]

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 14 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f80c5469-c092-4404-8c9c-e88650d1675e

📥 Commits

Reviewing files that changed from the base of the PR and between d06c1cb and d8d2ade.

📒 Files selected for processing (4)

• .jules/bolt.md
• CHANGELOG.md
• index.html
• tests/test_styles.py

---

_{Comment @coderabbitai help to get the list of available commands.}