Three Years of Accumulated Image Debt
When I finally ran a full audit using Google PageSpeed Insights on my 20 most-visited pages, the pattern was impossible to ignore. Every single page had images flagged as either too large, the wrong format, or both. My average page weight for a post with photos was 9.4MB. Average load time on mobile was just over 8 seconds. Three years of publishing without a single thought about image weight had built up quietly in the background, like sediment on a riverbed.
The most alarming discovery was not even the file sizes. It was the EXIF metadata. I had been publishing phone photos with full GPS location data embedded in every file. My home address was not in those images, thankfully, but my regular coffee shop was. The neighborhood where I filmed my social media content was logged in dozens of files sitting publicly on my server. That discovery alone would have been enough reason to do the cleanup.
How I Planned the Saturday Session
The night before, I downloaded all 180 images from my WordPress media library in a single batch export. I organized them into folders by post so I could re-upload them to the correct place afterward without any confusion. I gave myself the full day, set up my workspace with ImageBlink open in one browser window and my WordPress media library in another, and started at 9am with a clear process and a fresh coffee.
Work in batches by post, not by file type. Processing all images for one article at a time makes re-uploading faster and eliminates the risk of confusing which optimized image belongs to which article. The organizational overhead at the start pays off every time you re-upload.
The Exact Four-Step Process I Used
For each image, I ran the same consistent four-step sequence. Step one: use the image resizer to bring the width to 1000 pixels, the maximum content width in my blog theme. Step two: open the file in the EXIF viewer and strip all metadata before the file goes anywhere near a web server.
Step three: run each resized image through the JPEG compressor targeting under 120KB for standard in-post images and under 60KB for thumbnails. Step four: convert to WebP using the JPEG to WebP converter for any image used as a featured or hero image. The whole sequence took about 3 minutes per image once I was in a rhythm, which meant roughly 9 hours of focused work for 180 images.
What Happened to My Traffic Over the Next Month
By 6pm I had processed all 180 images and re-uploaded everything to the correct posts. My total page weight across the 20 most-visited articles dropped from an average of 9.4MB to under 800KB. Mobile load times fell from over 8 seconds to just under 2 seconds. My Google PageSpeed scores jumped from an average of 24 to an average of 71 across those pages. Numbers that had felt impossible to move for two years shifted in a single afternoon.
Over the following month, five posts that had been stuck on page two of Google moved up to page one. My average session duration increased by 40%. The work took one focused Saturday and cost nothing beyond my time. If you have a content-heavy site and have never done a serious image audit, this is almost certainly the highest-return project you are not doing.