You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that my Page get's very large if using the new Img Component. If using only a few Img Elements with each a few combinations of density, webp and sizes, the component will inline all alternative images from the srcset which are under 8Kb, even if they may never be used because of the wrong screen size or density. Hence that, I would suggest to turn off inlining of the images for the srcset by default or to add a new option which controls if the srcset alternatives should be inlined or not.
In my case I decreased my index page from 250kb to 80kb and increased the page speed from 60 to 95 just by lowering the inline limit to 1kb so that no alternatives are getting inlined.
The text was updated successfully, but these errors were encountered:
Thank you for the report 👍 Yes, I think it makes sense to disable automatic inlining if there are more than 1 images in the srcset. I'll do that in the next canary version.
I noticed that my Page get's very large if using the new Img Component. If using only a few Img Elements with each a few combinations of density, webp and sizes, the component will inline all alternative images from the srcset which are under 8Kb, even if they may never be used because of the wrong screen size or density. Hence that, I would suggest to turn off inlining of the images for the srcset by default or to add a new option which controls if the srcset alternatives should be inlined or not.
In my case I decreased my index page from 250kb to 80kb and increased the page speed from 60 to 95 just by lowering the inline limit to 1kb so that no alternatives are getting inlined.
The text was updated successfully, but these errors were encountered: