Skip to content

Optimize image by adding decoding & loading attributes 🖼 - #5012

Open
sanjaiyan-dev wants to merge 7 commits into
reactjs:mainfrom
sanjaiyan-dev:sanjaiyan-img-optimize
Open

Optimize image by adding decoding & loading attributes 🖼#5012
sanjaiyan-dev wants to merge 7 commits into
reactjs:mainfrom
sanjaiyan-dev:sanjaiyan-img-optimize

Conversation

@sanjaiyan-dev

Copy link
Copy Markdown
Contributor

Optimize <img />

  1. Adding decoding attribute with async value which decode the image asynchronously to reduce delay in presenting other content.
  2. Adding loading prop with lazy as a value which defers loading the image until it reaches a calculated distance from the viewport, as defined by the browser. The intent is to avoid the network and storage bandwidth needed to handle the image until it's reasonably certain that it will be needed.

Sorry if I made any mistakes :(

@github-actions

github-actions Bot commented Sep 7, 2022

Copy link
Copy Markdown

Size Changes

Details

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

Three Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load
/404 43.39 KB (🟡 +39 B) 127.68 KB
/500 43.37 KB (🟡 +39 B) 127.66 KB
/[[...markdownPath]] 43.46 KB (🟡 +39 B) 127.75 KB
Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants