Divi recommended configuration for server and hosting environment

Every WordPress installation, theme, plugin has its own requirements on server resources. Divi is both theme and plugin in a sense, a collection of an enormous amount of PHP code that works with many files at once and consumes memory accordingly to its size.

Minimum hosting environment recommendations for Divi

According to Divi Help & Support Center

PHP Version

Recommended: Latest

We recommend using the latest stable version of PHP. This will not only ensure compatibility with Divi, but it will also greatly speed up your website leading to less memory and CPU related issues.

memory_limit

Recommended: 128M

By default, memory limits set by your host or by WordPress may be too low. This will lead to applications crashing as PHP reaches the artificial limit. You can adjust your memory limit within your php.ini file, or by contacting your host for assistance. You may also need to define a memory limit in wp-config.php.

post_max_size

Recommended: 128M

Post Max Size limits how large a page or file can be on your website. If your page is larger than the limit set in PHP, it will fail to load. Post sizes can become quite large when using the Divi Builder, so it is important to increase this limit. It also affects file size upload/download, which can prevent large layouts from being imported into the builder. You can adjust your max post size within your php.ini file, or by contacting your host for assistance.

max_execution_time

Recommended: 180

Max Execution Time affects how long a page is allowed to load before it times out. If the limit is too low, you may not be able to import large layouts and files into the builder. You can adjust your max execution time within your php.ini file, or by contacting your host for assistance.

upload_max_filesize

Recommended: 64M

Upload Max File Size determines the maximum file size that you are allowed to upload to your server. If the limit is too low, you may not be able to import large collections of layouts into the Divi Library. You can adjust your max file size within your php.ini file, or by contacting your host for assistance.

max_input_time

Recommended: 180

This sets the maximum time in seconds a script is allowed to parse input data. If the limit is too low, the Divi Builder may time out before it is allowed to load. You can adjust your max input time within your php.ini file, or by contacting your host for assistance.

max_input_vars

Recommended: 3000

This setting affects how many input variables may be accepted. If the limit is too low, it may prevent the Divi Builder from loading. You can adjust your max input variables within your php.ini file, or by contacting your host for assistance.

You can find this information in the WordPress administration area when you log in.

In the admin menu go to Divi > Support Center and look for System Status panel. Green dots mean your configuration is OK, red dots mean you should address it and yellow means you should consider improvements. You are looking for: “Congratulations, all system checks have passed. Your hosting configuration is compatible with Divi.

Having these settings right should solve your most common hosting problems with Divi user interface, it does not mean your site is optimized for page speed and best performance, these are the common PHP settings that directly influence Divi functionality.

5 Responses

  1. Hi there, max input time and max execution time set to 180 seem to bee little too high, I am surprised, do you know why is this value recommended to 180 seconds?

  2. Bloom crashes WP on a local server environment. Of course this is the new generic 5.3 error: There has been a critical error on your website. Please check your site admin email inbox for instructions.

    Plus WordPress are removing these parameters as of 5.4.

    Can you suggest how the php.ini should look so Divi and Bloom can work?

    1. Hi Michael, php.ini might not be your problem in your case. Make sure you updated both Divi and Bloom to the latest version. We do not have any problems with Bloom on our hosting infrastructure, so I can’t relate.

      I can share a part of our php.ini with you:

      ****
      ; php.ini custom configuration directives
      php_value[disable_functions] = “opcache_get_status”
      php_value[error_reporting] = 22519
      php_value[max_execution_time] = 180
      php_value[max_input_time] = 180
      php_value[memory_limit] = 2048M
      php_value[open_basedir] = “/var/www/vhosts/example.com/:/tmp/”
      php_value[post_max_size] = 100M
      php_value[upload_max_filesize] = 100M

      ; Following directives define pool configuration
      pm = ondemand
      pm.max_children = 25
      pm.max_requests = 500
      pm.max_spare_servers = 1
      pm.min_spare_servers = 1
      pm.process_idle_timeout = 10s
      pm.start_servers = 1

      ****

      We use PHP FPM with Nginx as a reverse proxy for Apache, so it is very hard to give you php.ini advice.

Leave a Reply

Your email address will not be published. Required fields are marked *