Peregrine All case studies

Case study

Malcolm Kidd

malcolmkidd.co.uk

Every image in the library re-encoded to AVIF, with WebP behind it and the untouched original behind that. No redesign, no rebuild, and nothing deleted.

53.9%

less for a visitor to download, measured across 9 pages of the live site.

Before11.4 MB
Now5.3 MB
91images on the pages measured
76.1%off the image bytes themselves
6.2 MBremoved from an average visit
9pages weighed, not sampled

The heaviest page

Averages hide the page that actually hurts. On malcolmkidd.co.uk it is /gallery/, which went from 3.3 MB to 1.7 MB — 49.2% lighter. That is the page a visitor on a phone was waiting for.

Page by page

Every page, weighed as a browser loads it

HTML, stylesheets, scripts and images together — not a lab score and not a projection. Re-runnable at any time, because the page carries both halves of its own comparison: the AVIF a modern browser takes, and the original still sitting in the <img> fallback inside it.

PageBeforeNowLighter
Gallery3.3 MB1.7 MB49%
Cars vans for sale2.4 MB542 KB78%
Testimonials1.5 MB541 KB65%
Services1.3 MB498 KB63%
Home page1.2 MB534 KB57%
Terms conditions421 KB392 KB7%
Contact find us418 KB389 KB7%
2016 66 ford transit connect l2413 KB384 KB7%
2017 66 ford transit connect l1413 KB384 KB7%
Every page11.4 MB5.3 MB53.9%

The images alone came down 76.1%. The whole-page figure is lower because every page also carries text, layout and code, which this work does not touch — and the whole page is what a visitor waits for, so that is the number quoted at the top. Four of these pages offer several image sizes and the browser picks one by screen width, so those rows read the first candidate rather than a guaranteed download.

What was not done

Nothing was rebuilt, and nothing was thrown away

Originals are untouched

The AVIF and WebP files sit alongside the originals, never over them. Deactivate the plugin and the site serves exactly the bytes it did before, because those bytes never moved.

No browser is left behind

Serving uses <picture>. Anything that cannot read AVIF takes the WebP, and anything that cannot read either takes the original. Nobody sees a broken image.

The design did not change

Same theme, same layout, same photographs at the same dimensions. Put this against a screenshot from the week before and it should be indistinguishable.

Want the same measurement on your site?

The analyser fetches your real images and re-encodes them, so the figure you get is yours, not an average.

Test your site