Divi Essential 5.8.2 – WordPress Plugin

I tested Divi Essential on my own Divi setup, not on some clean fake demo site with three pages and zero clients yelling about CLS. It worked. Fully. No weird module limits, no “you can use this on one site only” nonsense in the package I tested — basically Unlimited Website Usage from a practical GPL point of view.

The annoying part? It still lives inside the Divi ecosystem, so you inherit all the usual Divi drama: fat DOM, builder previews randomly choking, and CSS specificity battles that make you question your career choices.

But honestly, Divi Essential saved me time. A lot of it.

What I actually liked

The good stuff is obvious once you open the Divi Builder. Divi Essential adds a pile of modules that Divi should’ve shipped years ago: content toggles, carousels, timelines, flip boxes, hotspots, modal popups, image masks, logo sliders, masonry galleries.

Most settings are where you expect them:

Edit Page -> Enable Visual Builder -> Add New Module -> Divi Essential modules

Styling is mostly under:

Design tab -> Typography / Spacing / Border / Box Shadow

Advanced tweaks are in:

Advanced tab -> Custom CSS

That part is nice. I didn’t have to write another cursed shortcode just to get a decent image carousel. Honestly, that alone made Divi Essential worth keeping on a client site where the budget was already bleeding.

The performance bit that made me swear

I opened Chrome DevTools, went straight to the Network tab, filtered by JS, and yeah — there it was. Extra frontend scripts, Swiper assets, animation stuff, and Divi’s own builder junk joining the party like nobody pays for hosting.

On my install, the plugin assets were loading from:

/wp-content/plugins/divi-essential/assets/

The main frontend files had handles similar to:

dnxte-frontend
dnxte-swiper
dnxte-magnific-popup

Not catastrophic, but if you use five animated modules above the fold, don’t act shocked when Lighthouse starts coughing blood.

I fixed part of it in:

Divi -> Theme Options -> Builder -> Advanced

I disabled static CSS file generation once during debugging, cleared everything, then enabled it back. Classic Divi ritual. Like sacrificing a goat, but with cache files.

Cache plugins: where things got stupid

With WP Rocket, Divi Essential broke my carousel when I enabled:

WP Rocket -> File Optimization -> Delay JavaScript execution

The carousel rendered as a sad vertical stack of images. No console explosion, just quiet failure, which is somehow more insulting.

My fix was to exclude these from delay:

jquery-core jquery-migrate et-builder-modules-script dnxte-frontend swiper

In WP Rocket that lives here:

Settings -> WP Rocket -> File Optimization -> Delay JavaScript execution -> Excluded JavaScript Files

After that, Divi Essential carousels behaved again. If you use LiteSpeed Cache, same idea:

LiteSpeed Cache -> Page Optimization -> JS Settings -> JS Delayed Excludes

Add the plugin frontend JS path there. Don’t overthink it. Divi and delayed jQuery are not friends.

What you can change in the builder

Most visual stuff in Divi Essential is editable without touching code:

• module spacing
• icon size
• image border radius
• carousel arrows
• overlay colors
• responsive typography
• animation timing
• button styling
• column layout per device

For mobile fixes, I mostly used:

Module Settings -> Design -> Sizing

and then hit the little phone icon beside width, margin, padding, font size. Divi hides responsive controls everywhere like it’s a treasure hunt designed by someone who hates wrists.

What still needs code

Some stuff is not worth fighting in the UI. I had a modal popup from Divi Essential that needed a custom close behavior after a form submit. No builder setting for that.

I added this in my child theme:

/wp-content/themes/divi-child/functions.php


add_action('wp_footer', function () {
    if (!is_page('contact')) return;
    ?>
    <script>
    jQuery(function($){
        document.addEventListener('wpcf7mailsent', function(){
            $('.mfp-close').trigger('click');
        });
    });
    </script>
    <?php
});

Ugly? Yes. Worked? Also yes.

If you need deeper changes, don’t edit plugin files unless you enjoy losing work on update. The module PHP lives around:

/wp-content/plugins/divi-essential/includes/modules/ The settings are stored like normal Divi content inside: wp_posts.post_content Global layouts sit in: wp_posts with Divi layout metadata scattered through: wp_postmeta So no, there isn’t a cute clean table called wp_divi_essential_settings. I wish.

FAQ

Why does the Divi Essential carousel show as stacked images?

Your JS delay/minify broke Swiper. Exclude jquery-core, swiper, dnxte-frontend, and et-builder-modules-script from delay.

Why does the Visual Builder freeze after adding several modules?

Usually DOM weight plus Divi being Divi. Disable browser extensions first, then clear: Divi -> Theme Options -> Builder -> Advanced -> Clear Also purge /wp-content/et-cache/.

Can I edit Divi Essential module HTML directly?

Not safely from the builder. You’ll need to inspect files under: wp-content/plugins/divi-essential/includes/modules/ Better solution: override with child theme JS/CSS unless you’re maintaining a fork.

Does Divi Essential make mobile pages heavier?

Yes, if you stack carousels, animations, hotspots, and popups like a maniac. Hide non-critical modules per device in: Advanced -> Visibility and stop loading three sliders on one landing page.