Case study
salifeline.org: 1,522 MB of images, served as 155 MB.
salifeline.org is a nonprofit’s WordPress site, and the first site to run ImgCrisp. Fullspec Studio builds and looks after it, so every release runs there first. Most of what went wrong with ImgCrisp was found there, too.
- Library
- 1,045 images
- Optimized
- 1,044
- Failed
- 0
- Skipped
- 1 (a GIF)
What visitors are sent
Each image on the site exists in several sizes, and ImgCrisp makes WebP and AVIF versions of every one. Added up across every size, this is what each kind of browser can be sent.
| Format | Total, every size | Versus originals |
|---|---|---|
| JPEG and PNG originals | 1,522 MB | |
| Served as WebP | 291 MB | 81% smaller |
| Served as AVIF | 155 MB | 90% smaller |
Measured in September 2026 across 954 optimized images and their 8,661 files. It’s a measure of the library, not of traffic: how much each visitor saves depends on the pages they open.
The site
A content site with a shop: WordPress with WooCommerce, the The7 theme, WPBakery and Slider Revolution. Themes and page builders like these print images in ways WordPress doesn’t expect, such as a full-size hero with no smaller sizes. That makes the site a hard first test.
What went wrong, and what changed
We said ImgCrisp would tell you what failed. Here is what failed on our own site.
An upscale was paid for on a page that never showed it.
The page’s template didn’t display its content, so nobody saw the sharper image. Since 0.19.0 the plugin checks each page’s public version before an upscale and flags images the page doesn’t show.
The first version of that check was wrong 50 times out of 53.
Members-only posts send visitors to a login page, and the check read the login page instead. Since 0.19.1 a page that redirects is left unmarked rather than flagged.
One upscale enlarged an image 4.5× and it showed.
At 3× the same kind of image stayed clean. Since 0.18.0 the confirmation warns before any enlargement past 3× and offers to upscale only the images measured as safe.
Crawlers were still downloading a 6.9 MB PNG.
The theme’s hero printed only the full-size file, and SEO crawlers that measure the plain image tag lowered the site’s score for it. Since 0.20.0 photo-like PNGs get a JPEG copy wherever the PNG would have gone: that hero is now 678 KB.
Each fix is in the changelog, under the release that shipped it.
Install it. Read the receipt. Undo it if you don’t like it.
Your first 50 images are free for 30 days. No card needed.
This page 60 KB on first load (phone, AVIF, fresh visit). How we measure