WALKSCAPE
Crosswave EditionEWWW Bulk Optimize and the WordPress Photos I Already Had
2026-01-01
When the media library begins to weigh on the site
After a while, a few WordPress photos become several hundred. When pages begin to feel slow, I check the cache and the host, then look at the size of the files the browser is actually downloading.
The first approach I tried was a familiar one.
Make each image smaller before uploading it.
I could make an upload lighter, but if I kept only that copy, the detail I discarded was gone. Bulk Optimize in EWWW Image Optimizer was useful once I started keeping originals and handling the site’s copies as a separate job.
Keep a source you can go back to
Resizing before upload can work if you keep the original elsewhere and give WordPress enough pixels for the uses you intend. Trouble begins when the small, compressed export is the only copy you have. WordPress may create additional sizes from it, and none can restore detail that was already lost.
With EWWW Image Optimizer, I could choose rules for new images and run the bulk tool over uploads that were already there. It scans the configured locations for files it can process, which saves having to upload the old library again.
Choose what the tool may change
Depending on the settings, EWWW can use lossless compression, resize images above chosen dimensions or remove metadata such as camera and location information. Resizing changes the image itself. Check the Preserve Originals option, keep a separate backup and decide whether you need to retain credits or other metadata.
A modest saving per picture can add up across a large library. For page speed, look at which file the browser actually loads and how many it loads. Savings on disk and savings on a page are related but separate measurements.
Why the bulk pass matters
Optimizing new uploads is one job. For a long-running site, the library you inherited from your own earlier work can be the larger one.
The current bulk tool can queue local images for optimization from WordPress. A big library still takes time and processing power. I would start with a backup and a small sample, check the resulting files and then run the larger job when the site is quiet.
When I would use it
A bulk run makes sense when the problem is measurable and the settings match what you are trying to preserve.
- You have hundreds of files that are larger than the pages need.
- You still have better originals for some older photos and want to improve the copies the site serves.
- You want to see whether lighter pages or more free disk space will help before paying for a bigger server.
- You want a consistent workflow for future uploads.
For old pictures that have already lost detail, look for the originals first. Compression can reduce the size of what is there. A better copy is what gives you back detail.
Make the next upload easier
The benefit of an optimizer is that it can make a repeatable part of publishing out of work you used to do differently on every photo.
I now keep original photographs separately and decide what dimensions the site needs before turning the optimizer loose on the library. A bulk pass is one part of that routine, alongside choosing the right image when a new story goes out.