Image optimization is the practice of delivering images at the smallest file size that maintains acceptable visual quality for the context in which they appear. Images typically constitute the largest share of page weight on content and commerce sites, which makes this among the highest-return performance work available and among the most consistently neglected.
Correct sizing is the largest single factor and the most commonly wrong. Serving an image at its full original dimensions when it will be displayed at a fraction of that size wastes bandwidth proportional to the difference in area, and the waste is invisible because the browser scales the image down and it looks correct. Auditing the ratio between delivered and displayed dimensions across a site routinely finds images several times larger than any display requires.
Modern formats deliver substantial savings at equivalent quality. WebP and AVIF both compress considerably more efficiently than the older formats they replace, with AVIF generally achieving the smallest files at the cost of slower encoding. Because browser support varies, the practical approach serves modern formats to browsers that accept them and falls back automatically, which the picture element and content negotiation both support without any loss of compatibility.
Responsive delivery ensures each device receives an appropriate version rather than one size for all. Providing several widths through a source set, with sizing information so the browser can choose before layout is complete, means a phone downloads a small image and a large display downloads a large one. Without this, either mobile devices download desktop-sized files or desktop displays show images that appear soft.
Compression settings involve a judgment that is usually made too conservatively. Lossy compression at moderate quality settings typically produces files substantially smaller than the original with differences that are imperceptible in normal viewing, and the instinct to preserve maximum quality frequently costs several times the file size for a difference nobody can see. Testing the actual perceptual threshold for a site's imagery, rather than defaulting to maximum quality, is worth the exercise.
Loading strategy determines when the cost is incurred. Images below the initial viewport should be deferred so they do not compete with content the visitor can actually see, while the image likely to be the largest element in the initial view should be loaded eagerly and given priority. Applying deferral indiscriminately, including to the hero image, is a common error that makes the primary loading metric worse.
Decorative imagery deserves scrutiny before optimization, since the cheapest image is the one not served. Large background photographs, carousel slides that most visitors never advance past, and stock imagery added to fill space all carry real cost and frequently contribute nothing to comprehension or conversion. Testing whether they earn their weight is a design question that precedes any technical work on delivery.
Layout stability requires that dimensions are declared. An image without specified width and height, or an equivalent aspect ratio, causes content to shift when it loads, which is both a measured penalty and a genuine irritation for anyone reading or reaching for a link. This is trivial to fix and remains one of the most common causes of layout instability.
Because the work spans content production, template implementation, and delivery infrastructure, durable improvement requires automation rather than manual discipline. In practice the audit and priorities sit within web performance work, automated transformation and responsive delivery are implemented through product development or handled at the edge by a delivery network, and the impact is greatest for e-commerce catalogues where every listing page carries dozens of images.