Download websites that use EWWW Image Optimizer

About EWWW Image Optimizer

Nobody redesigns a website in order to install an image optimizer. EWWW Image Optimizer arrives later, usually after a performance audit or a complaint about load times, and it works quietly inside the WordPress media pipeline, recompressing uploads as they arrive and rewriting existing libraries in bulk. The plugin therefore says less about what a site sells than about who looks after it.

Published by Exactly WWW under GPL v3 and written in PHP, the plugin has been part of the WordPress ecosystem since 2012, long enough to have accumulated two very different populations of users. One is the deliberate operator who chose it, tuned the compression level and connected the paid cloud conversion service. The other is the agency client who has never heard of the plugin at all, because a build shop puts the same performance stack on every site it ships. Reading a list of installs means holding both groups in mind at once.

As of October 2026 we detect EWWW Image Optimizer on 48,075 sites. Detection here is inferential rather than declared. A WordPress plugin announces itself through the asset paths, generated markup and occasional response headers it leaves behind, and a full page cache or a delivery network that rewrites image URLs can hide all of it. The figure should be read as a floor rather than a census, and sites with heavily rewritten asset pipelines are the ones likely to be missing from it.

The geography is what you would expect from a free plugin distributed through a global repository rather than sold through a channel. United States accounts for 15,288 of the installs we record, and domains ending in .com run through the whole list, which suggests the plugin travels with generic commercial hosting rather than with any national market. No reliable release string reaches us, so the dataset answers presence and not currency.

Two audiences ask for this population. Hosting companies and performance vendors want the addressable set of WordPress operators who have already admitted to an image weight problem, since a site running an optimizer has demonstrated intent that a site with untouched uploads has not. Competing plugin and service vendors want the same domains for displacement campaigns, because the install is the qualification. A per-domain lookup tells you whether one site runs the plugin. A downloadable list lets you ask the questions that only exist in aggregate, such as which hosts concentrate these installs, how the plugin co-occurs with page builders and commerce extensions, and which domains changed their stack between two snapshots.