Category: Getting Started Applies To: Divi Essential (All Plans) Last Updated: April 2026
Why This Article Exists
Divi Essential gives you access to 100+ powerful modules. That's incredible — but here's the thing: not every site needs all 100+ modules running at the same time.
Every active module loads its own CSS and JavaScript on your page, even if you're not using it on that specific page. Over time, this adds up. A site with all modules enabled is carrying a lot of extra weight it may not need.
That's exactly why the Module Manager exists — to give you full control over which modules are active, so your site only loads what it actually uses.
This guide walks you through everything: where to find it, how to use it strategically, and a practical checklist to get the best performance from Divi Essential.
What is the Module Manager?
The Module Manager is a control panel inside Divi Essential's settings that lets you enable or disable individual modules with a single toggle.
When a module is disabled:
- Its CSS is not loaded on your site
- Its JavaScript is not enqueued
- It does not appear in the Divi Builder module list
- It has zero performance impact
When a module is enabled:
- It's available in the Divi Builder
- Its assets load site-wide (on all pages, unless you use conditional loading)
Think of it like a circuit breaker panel — you control exactly which circuits are live.
How to Access the Module Manager
- Log in to your WordPress Admin Dashboard
- In the left sidebar, go to Divi Essential
- Click on Dashboard
You'll see a grid of all available modules, each with a toggle switch. Green or blue means active. Grey means disabled.
Understanding the Performance Impact
Here's a simplified breakdown of what happens when modules are enabled vs. disabled:
|
State |
CSS Loaded? |
JS Loaded? |
Available in Builder? |
|
✅ Enabled |
Yes |
Yes |
Yes |
|
❌ Disabled |
No |
No |
No |
Even if you haven't placed a module on any page, if it's enabled, its assets are still being enqueued. For a site with 80 active modules you're not using, that's significant dead weight.
Real-world impact:
- Fewer HTTP requests
- Smaller total page size
- Faster Time to First Byte (TTFB)
- Better Core Web Vitals scores
- Improved Lighthouse / PageSpeed scores
A Practical Strategy: Enable Only What You Use
Instead of keeping everything on by default, follow this simple approach:
Step 1 — Audit your active modules
Go through your site page by page and make a list of every Divi Essential module you're actually using. Be honest — if you tried a module once for a test page that no longer exists, it doesn't count.
Common modules used on most sites:
- Multi Heading
- Gradient Text
- Flip Box
- Masonry Gallery
- Timeline
- Reading Progress Bar
- Table of Contents
Modules that are situational (only enable if you need them):
- Facebook Page / Like / Comment / Embed
- Twitter Timeline / Follow
- PayPal Button / Stripe Button
- Gravity Forms / Contact Form 7
- 3D Spline
- Lottie
Step 2 — Disable what you don't use
In the Module Manager, go through the list and toggle off any module you identified as unused.
A good rule of thumb: if you haven't used it in the last 3 months, disable it.
You can always re-enable a module in seconds — so there's no risk in turning things off.
Step 3 — Save your changes
After making your selections, click Save Changes. The changes take effect immediately.
Step 4 — Test your site
After saving, quickly browse through your key pages to confirm everything still looks correct. Since you've only disabled modules you identified as unused, nothing should break — but it's always worth a quick check.
Optionally, run a PageSpeed Insights or GTmetrix test before and after to see the improvement.
Pro Tips
💡 Tip 1 — Disable social modules if you don't embed social content Facebook and Twitter embed modules load external SDKs from Meta and Twitter's servers. Even when idle, these affect your privacy score and can slow down page load. Disable them unless you're actively using social embeds.
💡 Tip 2 — Use a staging environment first. Before disabling modules on a live site, test on a staging environment. Confirm no page breaks, then apply the same changes to production.
💡 Tip 3 — Re-enable is instant. There's no penalty for enabling a module, using it for a project, then disabling it again. The Module Manager is designed to be toggled freely.
💡 Tip 4 — Pair with a caching plugin After updating your Module Manager settings, clear your caching plugin (WP Rocket, LiteSpeed Cache, W3 Total Cache, etc.) to ensure the new, lighter asset bundle is served to visitors.
💡 Tip 5 — Revisit after major site updates. Any time you do a major site redesign or add new pages, revisit the Module Manager. You may have added new module usage, or removed old pages that were the only place a module was being used.
Common Questions
Q: Will disabling a module remove it from pages where I've already used it?
A: No — the module's content stays in place in your database. However, it won't render correctly on the front-end until you re-enable it. For this reason, audit carefully before disabling.
Q: Does disabling a module affect the Divi Builder editor?
A: Yes — disabled modules will no longer appear in the Divi Builder's module search or insert panel. This actually makes the builder cleaner and faster to navigate, too.
Q: Does this affect performance on every page or just some pages?
A: By default, Divi Essential assets load site-wide. Disabling a module removes its assets from all pages. This is the most impactful approach for overall site performance.
Q: I disabled a module, and now something looks broken. What do I do?
A: Re-enable the module immediately. Then check which pages were using it. Either keep the module enabled or replace it with an alternative before disabling it again.
Summary
The Module Manager is one of the most underused features in Divi Essential — yet it's one of the highest-impact changes you can make for site speed.
Here's the three-line version:
- Audit which modules you're actually using on your live site
- Disable everything else in the Module Manager
- Clear your cache and test
You don't need to use all 100+ modules to get value from Divi Essential. You just need the right ones — and the Module Manager lets you run exactly that.