next/image-fill-sizes

Dlaczego

With fill, the image has no width of its own, so Next.js generates a srcset for every device width. Without sizes the browser assumes the image is as wide as the viewport (100vw) and picks a file to match: a card thumbnail 300 px wide downloads a 1,920 px image on a desktop screen, which costs data and delays the Largest Contentful Paint.

Poprawka

Describe the rendered width per breakpoint, matching your CSS: sizes="(max-width: 768px) 100vw, (max-width: 1200px) 50vw, 33vw". Use sizes="100vw" only for images that really span the viewport. Give the parent position: relative (or fixed/absolute) and a size.

Przykłady

// bad
<Image src={product.photo} alt={product.name} fill />
// good
<Image src={product.photo} alt={product.name} fill sizes="(max-width: 768px) 50vw, 25vw" />

Źródła

• Next.js docs, Image component (sizes)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain next/image-fill-sizes