Skip to main content
Divi Builder Timeout Error

The Divi Builder TImeout Error occurs when the builder fails to load because of an unknown error.

Updated over a week ago

Note: This troubleshooting guide may require that you make server-side changes to your website. If you are not comfortable making those changes, you will need to contact your hosting provider for assistance.

The Divi Builder Timeout error occurs when the Divi Builder fails to load because of some error. Listed below are a few common things that can cause this error to occur.

PHP Limits

Each website environment is set up differently and hosting providers can limit PHP directives value for various reasons.  

Here is a list of minimum required configuration directives that are optimal for running a WordPress website:

memory_limit 128M
post_max_size 64M
max_execution_time 120
upload_max_filesize 64M
max_input_time 60
max_input_vars 1000

Above are the minimum requirements, however, the higher the values, the better the performance.

PHP Version

We recommend running the PHP 7.4+ version. Most hosting providers have an option to change the PHP version from their cPanel, however, if that is not the case you can always reach out to them and they should be able to take care of it for you.

Note: Most hosting providers can assist you with adjusting your above PHP Limits


Caching is a very complex set of systems that can easily cause conflicts between scripts. Make sure to always clear all your caches once a plugin, theme and the WordPress core have been updated.

Cache may include:

  • Plugin Cache (Check your active cache plugins and clear cache from the plugin settings)

  • CDN Cache (Check your server cache CDN settings or CDN plugin settings)

  • Server-side Cache (Check your server cache settings)

Check with Plugin(s) Conflict, Child Theme Conflict or Customization Conflict.

Divi has a feature to check the site in Safe mode.

You can go to WordPress Dashboard > Divi > Support Center and enable the Safe Mode:

Note: Enabling Safe Mode will temporarily disable customizations and plugins that may be causing problems with your Elegant Themes product. This includes all Plugins, Child Themes, and Custom Code added to your Theme Options integration areas. These items are only disabled for your current active user session so your visitors will not be disrupted. Enabling Safe Mode makes it easy to figure out what is causing problems on your website by identifying or eliminating third-party plugins and code as potential causes.

Enabling the Safe mode, check the Divi Builder again. If Divi Builder works fine on Safe mode, this confirms one of the following conflicts is causing the issue.

Disable the Safe mode and perform the following tests:

Plugin(s) Conflict

Sometimes plugins can conflict with a theme or with each other. 

Disable all your plugins and see if the problem persists. If everything is working once the plugins were disabled it means there's a conflict with a plugin or maybe even a set of plugins.
Enable the plugins one by one to identify the one that is creating the conflict.

Child Theme Conflict

To test for a child theme conflict you can temporarily disable the child theme by going to Appearance > Themes and enabling Divi (the parent theme).

Custom Code Theme Options > Integration Conflict

To test the conflict with Theme Options > Integration codes, you can temporarily disable all the codes from these options:

Then test with Divi Builder again.

If the Divi Builder works, this confirms one of the code is causing the issue, you may want to enable them individually and check which code is giving the conflict.

Use the latest version

Make sure that you are running the latest version of Divi, Extra or the Divi Builder plugin.

Consider switching to Divi Hosting

We partnered with our favourite WordPress hosts to create the best hosting solution for Divi. On Divi Hosting, PHP limits are already sufficient, so you don't need to worry about Divi Builder timeout errors. Plus Divi Hosting comes with Divi pre-installed and activated automatically 😄

Did this answer your question?