If you search for image compression plugins on WordPress.org, you will find dozens of options. EWWW Image Optimizer has been around since 2012. Smush has over a million installs. ShortPixel has 300,000. TinyPNG is a household name.
All of them work with WordPress. None of them were built for Divi.
This matters more than it might seem. Divi, especially Divi 5, has a specific way of handling images that generic compression plugins are not designed for. In this article we explain why that gap exists, what it means for your site's performance, and why Divi Image Compressor was built to close it.
How Divi Handles Images Differently
Divi Registers Its Own Image Sizes
Standard WordPress registers a handful of image sizes: thumbnail (150×150), medium (300×300), medium-large (768px wide), and large (1024px wide). Every image you upload generates all of these automatically.
Divi adds its own image sizes on top of those — sizes specific to Divi modules like the portfolio grid, blog module, and fullscreen backgrounds. When you upload an image to a Divi site, you are not generating 4–5 thumbnail sizes. You are generating 8–12, depending on which Divi modules you use.
A generic compression plugin that processes images at upload time may not hook into the WordPress pipeline at the right moment to catch all of Divi's custom sizes. The original gets compressed. The Divi-specific thumbnails may not.
Divi 5 Uses a React-Based Visual Builder
Divi 5 is a ground-up rewrite of the Divi builder, built on React. The Visual Builder renders pages differently from Divi 4's classic approach, and the order in which filters and actions fire during upload can differ from what generic plugins expect.
A plugin written in 2014 and incrementally patched since then — which describes most of the major image optimisation plugins — was not tested against Divi 5's architecture. Conflicts are uncommon but not unheard of, particularly around how the media library behaves when the Visual Builder is active.
Divi Fullscreen Images Need Maximum Compression
Divi's most impactful design patterns — full-width hero sections, fullscreen row backgrounds, parallax sections — all rely on large images. A 4000×2000 hero image at full resolution can easily weigh 4–5MB. These are precisely the images that most affect your Core Web Vitals score, and they are the images that generic plugins are least likely to handle correctly, because they often have maximum file size restrictions.
EWWW Image Optimizer's free tier, for example, has no explicit file size limit on local compression, but its cloud-based tiers do impose limits. Smush's free version cannot process images over 5MB at all.
The Problem with EWWW Image Optimizer for Divi Sites
EWWW Image Optimizer is the most commonly recommended "local" alternative to cloud-based plugins — and its local processing model is genuinely a selling point. It compresses images on your own server without an external API, using open-source tools like cwebp, optipng, and jpegtran.
For developers comfortable with server administration and command-line tools, EWWW is a powerful option. But it has significant friction for the typical Divi user:
Setup complexity. EWWW works best when native binaries (cwebp, jpegtran, etc.) are installed on the server. On managed hosting environments — SiteGround, Kinsta, WP Engine, Flywheel, Cloudways — installing these binaries is often not possible or requires support ticket escalation. Without the binaries, EWWW falls back to PHP-based processing, which is slower and produces less efficient output.
Configuration overhead. EWWW's settings panel has options for force re-optimise, metadata removal, lossless vs lossy per file type, WebP rewrite rules (via .htaccess or JavaScript), server paths for custom binary locations, and an API mode that routes processing to their cloud service. For a Divi designer whose core job is building pages, this is an unnecessary cognitive load.
WebP delivery requires manual .htaccess configuration. EWWW can convert images to WebP, but serving those WebP files to browsers requires adding rewrite rules to your .htaccess file. Get the rules wrong and you have broken image delivery. On Nginx servers the rules are different again. The plugin includes helpers for this, but it is still a setup step that generic plugins require and Divi Image Compressor does not.
No Divi-specific integration. EWWW is a generic WordPress plugin. It does not know about Divi's image sizes, Divi's module structure, or Divi 5's Visual Builder. It compresses what WordPress tells it to compress and has no awareness of the Divi ecosystem.
What a Divi-Specific Approach Looks Like
Divi Image Compressor was designed around three principles that matter specifically for Divi users:
- Automatic compression of everything Divi generates. Divi Image Compressor hooks into the WordPress wp_handle_upload pipeline at a priority that ensures both WordPress core image sizes and Divi's custom sizes are compressed correctly on upload. You do not need to think about which thumbnail was missed.
- WebP served automatically — no .htaccess required. When WebP conversion is enabled, Divi Image Compressor converts the image to WebP and stores it alongside the original. WordPress (from version 5.8 onwards) handles WebP delivery natively in the block editor and in most contexts. For Divi's own image rendering, the plugin ensures WebP files are referenced correctly without requiring manual server configuration.
- Local processing without binary installation. Unlike EWWW, Divi Image Compressor uses PHP's GD Library and ImageMagick — both of which are pre-installed on virtually every managed WordPress host. No command-line access required. No binary paths to configure. No .htaccess rules to write. Install the plugin, set your quality level, and it works.
How Divi Image Compressor Compares to EWWW
Recommended for Divi
Divi Image Compressor
$29.99 yearly
EWWW Image Optimizer
Free (limited)
Which Image Types Matter Most on a Divi Site
Understanding what to compress — and how aggressively — is where Divi-specific knowledge pays off. Here is a practical guide for the image types common to every Divi build:
Hero and fullscreen background images. These are your largest files and have the most impact on your Lighthouse score. Use WebP with quality 75–80. Divi Image Compressor will compress and convert these automatically. Aim to keep them under 200KB.
Portfolio and gallery images. These are displayed at medium sizes in Divi's grid modules. Quality 80 is appropriate. WebP conversion reduces them significantly without visible degradation.
Blog featured images. Displayed across archive pages, category pages, and blog modules. Keeping these small improves perceived load time across your entire blog. Quality 80, WebP on.
Team and person images. Usually circular or portrait-cropped thumbnails. Quality 85 preserves facial detail well.
Logos and icons in Divi modules. These should remain as PNG (for transparency) or SVG. Divi Image Compressor applies lossless compression to PNGs by default, preserving sharp edges.
The Bottom Line
If you are serious about page speed on a Divi site — and given that Google's Core Web Vitals directly affect search rankings, you should be — the image compression plugin you choose matters.
Generic plugins like EWWW, Smush, and ShortPixel are capable tools for generic WordPress sites. They were not built for Divi, they do not know about Divi's image pipeline, and their setup complexity is often at odds with the streamlined workflow Divi users expect.
Divi Image Compressor does one thing: compresses and converts every image on your Divi site, automatically, on your own server, without any setup beyond installing the plugin. For Divi 4 and Divi 5 sites, that is exactly what you need.
Divi Image Compressor is available as a one-time purchase on the Elegant Themes Divi Marketplace. There are no subscriptions, no API keys, and no limits on how many images you can compress.
Divi Image Compressor is developed by DiviPerfect — a suite of Divi 5 plugins built for freelancers, agencies, and businesses. Questions? Email us at hello@diviperfect.com or visit diviperfect.com.