Skip to content

perf: serve the shared hero in modern image formats #198

Closed

Description

@devantler

🤖 Generated by the Daily AI Engineer

Part of #176.

Problem

The latest ten successful main Lighthouse runs still miss the guest-facing budgets: homepage LCP is about 4.14 s against 2.5 s, while login LCP is about 3.01 s. A fresh current-main trace identifies the shared 146 KB, high-priority /gl-brydegaard.jpg background as the strongest remaining quantified opportunity: modern encoding avoids about 95 KB and Lighthouse estimates roughly 450 ms of LCP savings.

Both guest entry pages use this image above the fold. First-time guests on slower mobile connections therefore spend avoidable time downloading a larger legacy asset before the page settles.

Expected behaviour

Modern browsers should receive a materially smaller AVIF hero immediately, with WebP and the original JPEG retained as safe fallbacks. The visual treatment, crop, content, accessibility, and CSP posture must remain unchanged.

Acceptance criteria

  • /, /login, and the error page use native <picture> source selection with AVIF, WebP, and JPEG fallback.
  • / and /login preload the AVIF with the correct MIME hint and high fetch priority.
  • The AVIF is under 60 KB; Chromium requests it without also fetching the JPEG.
  • Browsers that do not support AVIF select a compatible fallback without downloading an unused AVIF.
  • Lint, type checks, unit tests, bundle budget, full Playwright, CSP, and accessibility checks pass.
  • Mobile and desktop user checks preserve crop, readability, and perceived image quality.
  • A matched local Lighthouse comparison shows a material LCP improvement without regressing FCP, CLS, or TBT.

Rough size

S — two encoded assets, one shared background component, three consumers, and focused E2E coverage.

Activity

  1. coderabbitai commented on Jul 17, 2026

    @coderabbitai
    🔗 Related PRs

    #148 - ci: serve the Lighthouse lane via vite preview to fix its cold-start hang [merged]
    #174 - feat(security): serve a Content-Security-Policy and HSTS [merged]
    #177 - perf(gallery): defer off-screen carousel slides [merged]
    #178 - perf: preload the hero LCP background image [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. botantler-1 commented on Jul 17, 2026

    @botantler-1
    Contributor

    🎉 This issue has been resolved in version 1.15.6 🎉

    The release is available on GitHub release

    Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions