Divi Builder Timeout Warning: Step-by-Step Fix

If you use the Divi theme or Divi Builder plugin, you’ve likely seen the “The Divi Builder could not complete the request” timeout warning. This happens when WordPress’s AJAX request limit is too low for Divi’s complex operations, often on slower servers or large pages. This guide walks you through the most effective fixes, from simple plugin updates to server-level adjustments, so you can get back to building without interruptions.

What You’ll Need

• Admin access to your WordPress dashboard
• FTP or cPanel File Manager access (for editing wp-config.php and .htaccess)
• A code editor (like Notepad++) or the built-in file editor in cPanel
• Ability to install plugins (or you can edit files directly)

Step-by-Step

1. Update Divi and WordPress. Outdated versions often cause compatibility issues. Go to Dashboard → Updates and update WordPress core, then go to Divi → Updates to update the theme and builder. Also update any other plugins that might conflict.
2. Increase WordPress memory limit. Divi is memory-hungry. Edit your wp-config.php file (located in your site’s root directory) and add or modify this line:
   define('WP_MEMORY_LIMIT', '256M');
   Place it just before the line that says /* That's all, stop editing! Happy publishing. */. Save and re-upload the file.
3. Increase PHP execution time. The timeout warning is often caused by PHP’s max_execution_time being too low. You can change this in your wp-config.php as well. Add this line:
   set_time_limit(300);
   This sets the limit to 300 seconds (5 minutes). If that doesn’t work, you may need to edit your php.ini file (if you have access) and set max_execution_time = 300.
4. Increase AJAX timeout in Divi. Divi has its own AJAX timeout setting. Go to Divi → Theme Options → Builder → Advanced. Look for “AJAX Timeout” and increase it from the default (usually 30 seconds) to 120 seconds or more. Save changes.
5. Disable conflicting plugins. Some plugins, especially caching or security plugins, can interfere with Divi’s AJAX requests. Temporarily deactivate all plugins except Divi (and its required plugins). If the warning disappears, reactivate them one by one to find the culprit. Once found, either replace it or add an exception for Divi in its settings.
6. Switch to a default WordPress theme. To rule out a theme conflict, temporarily switch to a default theme like Twenty Twenty-Four. If the issue goes away, your theme (not Divi) is causing the problem. You can then re-enable Divi and contact Elegant Themes support.
7. Increase server resources (if you have cPanel). In cPanel, look for “MultiPHP INI Editor” or “Select PHP Version”. Increase memory_limit to 256M, max_execution_time to 300, and max_input_time to 300. Save and test.
8. Edit .htaccess to increase timeouts. If you’re on Apache, add these lines to your .htaccess file (in the root directory):
   php_value max_execution_time 300
php_value max_input_time 300
php_value memory_limit 256M
   Save and test. If you get a 500 error, remove the lines immediately.
9. Clear all caches. After making changes, clear your browser cache, any caching plugin (like WP Rocket or W3 Total Cache), and server-side caches (like Varnish or CDN). This ensures the new settings are actually used.
10. Repair the Divi Builder database tables. Occasionally, corrupted Divi database tables cause timeouts. Install a plugin like “WP-DBManager” or use phpMyAdmin to repair all tables. In phpMyAdmin, select your database, check all tables, and choose “Repair” from the dropdown.

Common Mistakes

• Editing the wrong wp-config.php. Make sure you’re editing the file in the root of your WordPress installation, not a subfolder or a backup.
• Using 256M when your server only allows 128M. If you set a memory limit higher than your server’s hard limit, you’ll get a fatal error. Start with 128M and work up.
• Not clearing caches after changes. Even if you’ve updated the settings, a stale cache can still cause timeouts.
• Deactivating all plugins without a plan. If you deactivate everything and the problem goes away, you need to reactivate them systematically to find the culprit. Don’t just leave them all off.
• Forgetting to save changes in the Divi Theme Options. The AJAX timeout field is easy to miss. Double-check that you clicked “Save Changes” at the bottom of the page.

Tips

• Use a child theme. If you’re making code changes, a child theme prevents your modifications from being lost when Divi updates.
• Optimize your images. Large images can slow down the builder. Compress images before uploading to reduce the load on the server.
• Consider a faster hosting provider. If you’re on shared hosting, moving to a managed WordPress host or a VPS can dramatically reduce timeouts.
• Keep Divi and WordPress updated regularly. Updates often include performance improvements and bug fixes related to timeouts.
• Use a staging site. Test any changes on a staging site first to avoid breaking your live site.

Troubleshooting

If you’ve followed all the steps and still see the timeout warning, try these additional checks:

• Check the browser console. Press F12 to open developer tools, go to the “Network” tab, and look for failed requests. The error message may give you a clue about what’s failing.
• Check the server error logs. In cPanel, look for “Error Logs” or “Raw Access Logs”. Look for PHP errors or memory exhaustion messages around the time of the timeout.
• Disable CDN. If you’re using a CDN like Cloudflare, temporarily disable it. Sometimes CDNs strip headers that Divi needs.
• Increase PHP memory further. Some complex pages need 512M. Try that if 256M doesn’t work.
• Contact your hosting provider. If you’ve exhausted all options, your host may have restrictions on execution time or memory that you can’t override. Ask them to increase the limits for your account.

Frequently Asked Questions

Why does Divi Builder timeout happen?

It happens when the server takes longer to process a request than the allowed time limit. This is often due to low PHP execution time, insufficient memory, or a slow server.

Will increasing the memory limit break my site?

No, as long as you don’t exceed the server’s hard limit. If you set it too high, you’ll get a fatal error, but you can easily revert the change.

Do I need to edit .htaccess if I already edited wp-config.php?

Not necessarily. wp-config.php is the primary place to set PHP limits. .htaccess is an alternative if you don’t have access to wp-config.php or if your server ignores the PHP settings in it.

Can I fix this without any coding?

Yes, you can install a plugin like “WP Increase Memory Limit” or “WP Maximum Execution Time Exceeded” to adjust these settings from the dashboard. However, editing files manually is more reliable.

Why does the warning only appear on certain pages?

Pages with lots of content, images, or complex modules require more resources. The timeout is more likely on those pages.

Will this fix work on any hosting?

Most steps work on any hosting, but some shared hosts restrict PHP settings. If you can’t change them, contact your host.

Related

• Enable Mojave on Older Mac: Full Compatibility Guide
• Enable RPM Fusion Repositories in Fedora
• Check UPI Payment Status in Merchant Account