You click “Enable Visual Builder.” The screen dims. A spinner appears. And spins. And spins. Nothing happens. You are stuck. This is one of the most common Divi frustrations. The good news: it rarely takes more than two minutes to fix.
Why Divi Builder Gets Stuck
The Visual Builder loads a separate interface on top of your page. It requires JavaScript to communicate with your server. If something blocks that communication – a security plugin, a caching plugin, or even a conflicting script – the builder never finishes loading.
In most cases, the culprit is a plugin that adds code to every page without telling you [citation:1].
The 2-Minute Fix
Before you try anything else, do this:
- Open your browser’s developer tools (F12 on Windows, Cmd+Option+I on Mac)
- Click the “Console” tab
- Look for red error messages
The console will tell you exactly what is breaking. Common errors include:
- “Failed to load resource” – a file is blocked or missing
- “Uncaught TypeError” – JavaScript conflict with another plugin
- “401 Unauthorized” – security plugin blocking the request [citation:5]
If Console Shows No Errors
Try these steps in order:
- Clear your browser cache – sometimes the simplest fix works [citation:9]
- Try a different browser – if it works in Chrome but not Opera, your browser is the issue [citation:9]
- Disable caching plugins temporarily – WP Rocket, Hummingbird, and others can interfere [citation:9]
- Check for plugin conflicts – deactivate all plugins except Divi, then re-enable one by one
The “Display: None” Workaround
If a specific plugin is blocking the builder and you cannot deactivate it, add this CSS to Divi Theme Options → General → Custom CSS:
.admin-bar .et-fb-root-ancestor-sibling#plugin-name {
display: none !important;
}
Replace “plugin-name” with the ID of the conflicting plugin. This hides the plugin’s elements from the builder interface without deactivating it [citation:1].
When Nothing Works
Use the Backend Builder instead. Go to Pages → Edit Page → Use Divi Builder (Backend). It is not as pretty as the Visual Builder, but it works when the frontend version refuses to load.