Dev.to WebDev 🛠 Dev 👁 0 📖 1 min read

A PNG Wearing a .webp Filename Cost My Services Page 441 KiB

The one optimization that moved the numbers on my Services page was rebuilding a single image — because the file was not what its name said it was. PageSpeed flagged about 441 KiB of "improve image delivery" waste on th

The one optimization that moved the numbers on my Services page was rebuilding a single image — because the file was not what its name said it was.

PageSpeed flagged about 441 KiB of "improve image delivery" waste on that page in October. When I looked, the image was a 469 KB PNG wearing a ".webp" filename, and WordPress was still offering the big file to phones through srcset. So I converted it to a real WebP at quality 80 — 37.6 KB, 92% smaller — uploaded it as a new attachment, and removed the srcset so the old PNG could not be served again.

Measured on mobile PageSpeed, same tool and same slow-4G emulation: the page went from 72 to 85, and Largest Contentful Paint from 6.3 seconds to 3.5 seconds, with the image-delivery audit now passing. I am quoting the settled re-test after the caches rebuilt — one run a minute after purging read 58, which was a cold-cache artefact, and scores swing about ±10 between runs anyway.

I will not oversell it: 3.5 seconds is still above the 2.5-second "good" bar for LCP, and with no real traffic yet there is no field data, so this is a lab improvement, not a proven ranking gain. But it was the clearest lesson of the audit — check what the file actually is, not what it is called.

— Masood Ahmad, Editor, Dentist in Pico Rivera (dentalpicorivera.com)

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.