Skip to content

Fix/issue 3885 next image#3902

Open
pradeep0153 wants to merge 22 commits into
Premshaw23:masterfrom
pradeep0153:fix/issue-3885-next-image
Open

Fix/issue 3885 next image#3902
pradeep0153 wants to merge 22 commits into
Premshaw23:masterfrom
pradeep0153:fix/issue-3885-next-image

Conversation

@pradeep0153

Copy link
Copy Markdown
Contributor

Closes #3885.

Description

This PR drastically improves the application's visual loading performance by migrating standard HTML image elements over to the heavily optimized Next.js <Image> component.

Changes Made

  • Audited the app/ and components/ directories for hardcoded HTML <img> tags.
  • Replaced these tags with next/image, correctly configuring the src, alt, width, and height properties to prevent cumulative layout shifts (CLS).

Impact

  • Core Web Vitals & Bandwidth: Standard <img> tags force the browser to download full-resolution images upfront, which severely hurts the Largest Contentful Paint (LCP) metric. By leveraging the <Image> component, images are now automatically resized for the user's specific device, served in modern next-gen formats like WebP or AVIF, and lazily loaded as they scroll into the viewport, saving significant bandwidth and drastically speeding up initial page loads.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Perf: Replace standard <img> tags with Next.js <Image> component

1 participant