Web Performance

Image CDN

A CDN that also resizes, re-formats and compresses images on the fly, per request.

An image CDN serves images from an edge network and transforms them per request — resizing to the size actually displayed, converting to WebP or AVIF when the browser supports it, and compressing appropriately. It replaces the build-time work of generating every variant by hand, which is why most sites' images are the wrong size without one.

Definition

Beyond caching, an image CDN reads request parameters and headers to decide what to return: dimensions from the URL, format from the Accept header, quality from a policy.

The value is that correctness stops depending on discipline. A designer uploading a 4000-pixel photograph still results in an appropriately sized, modern-format image being delivered.

Why It Matters

Images are usually the largest part of page weight, and the most common failure is serving one far larger than it is displayed at. An image CDN removes that failure mode structurally.

Example

/image/hero.jpg?w=800&fm=auto returns an 800-pixel-wide AVIF to a browser that accepts it and a JPEG to one that does not, from the same source file.

What it removes is a class of human error

The value of an image CDN is not primarily the edge caching; it is that correctness stops depending on whoever uploads the file.

Without one, serving the right image requires someone to resize before upload, convert to a modern format, generate the variants, and reference the right one in the right context — every time, across everyone who touches the site. In practice that discipline fails, which is why oversized images are the most common performance finding on almost every platform.

With one, a designer uploading a 4000-pixel photograph still results in an 800-pixel AVIF being delivered to a phone, because the transformation happens per request based on the URL parameters and the browser's Accept header.

How SlapMyWeb checks this

The audit reports every image's transfer size against the dimensions it is displayed at, so an image served at four times its rendered width is flagged with the saving available. It does not require a CDN — what it measures is whether the delivered file is appropriate for its display, which an image CDN achieves structurally and a disciplined build process can achieve manually.