← All work

Case study · Web performance · Process

Cutting the image footprint by ~80%

How I took Beer Hawk's (now PerfectDraft's) Magento 2 store from print-resolution uploads to automatically optimised WebP images, starting with fixes by hand and ending fully automated.

Role
Senior Front-End Developer & team lead
Company
PerfectDraft · AB InBev
Timeline
2018 onwards
Tools
Magento 2 · TinyPNG · TinyCDN · WebP

Average image file size

−80%

  • Before 100% · print-ready originals
  • After 20% · optimised WebP

01 / The problem

Print files on a web store

Product and marketing images came from high-resolution artwork used across print and other media: 300dpi originals, tens of thousands of pixels wide, saved as PNG, JPG or TIFF. Marketing and Design were used to designing for print, not the web, so new images usually arrived far too big and in the wrong format.

I spotted the problem a couple of months after joining Beer Hawk, usually when a new product upload made a page slow to load, and kept pushing until it was fixed properly.

02 / What I did

From manual fixes to automatic

  1. Step 1: Fixed images by hand

    Whenever a slow page turned up, I resized the image, changed its format and compressed it with TinyPNG.

  2. Step 2: Taught the design team

    Showed Marketing and Design how to create web images at the right size and resolution, and which format suits which purpose.

  3. Step 3: Automated it with TinyCDN

    Moved images onto TinyCDN, which hosts and optimises them in one step, so nobody had to fix uploads by hand any more.

  4. Step 4: Switched delivery to WebP

    Converted every image on the site to WebP for delivery, for smaller files at the same visual quality.

[Caption: the same page, before and after.]
[Caption: what the design team worked from.]

03 / Outcome

What changed

smaller image files, on average
~80%
pages, and noticeably so
Faster
SEO rankings and PageSpeed scores
Higher
habits: the design team kept to the rules, and asked when unsure
Lasting

04 / The trade-off

Worth the cost

The CDN added a running cost. It was easily covered by the time saved: nobody was spending hours checking and fixing images by hand any more.

  • Web performance
  • WebP
  • CDN
  • Technical SEO
  • Training
  • Magento 2
Next case study cv-gen: tailored applications that stay honest

Is your site slower than it should be?

hello@robertwood.me