perf: migrate external images to Next.js Image - #100
Merged
Lakes41 merged 1 commit intoJul 29, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Migrates all production image rendering from standard HTML
<img>elements to Next.js<Image />.The new shared image component provides explicit dimensions, lazy loading, WebP optimization for approved remote hosts, blur-up placeholders, and graceful fallbacks when remote images fail to load.
Linked Issue
Closes #62
Type of Change
Summary of Changes
ImageWithFallbackcomponent with fixed dimensions, lazy loading, blur placeholders, and URL-aware error recovery.<img>elements to Next.js<Image />.<img>elements remain in production source files.Test Evidence
The following checks were run: