Is Asset CleanUp loading when Divi Builder is used? How to make the editor faster?

Note: This option is available in the Pro version 1.1.9.2.

By default, Asset CleanUp Lite/Pro does not trigger its unload rule when Divi’s builder is in use. Moreover, no extra Asset CleanUp Lite/Pro optimization rule takes place including minifying/combining CSS/JS. The reason behind it is to make sure that the editor will load perfectly fine, and none of its assets that are built especially for the visual builder are altered in any way.

Whenever the following query strings are used, Asset CleanUp Lite/Pro doesn’t trigger its unload rules by default (unless you make an exception by following the instructions mentioned below):

  • /?et_fb=1&PageSpeed=off&et_tb=1
  • /?et_pb_preview=true&et_pb_preview_nonce=[…]
  • /wp-admin/admin.php?page=et_theme_builder

There have been plenty of situations when some of the builder’s files were altered (e.g. minified) that ended up in the page builder not loading due to JavaScript errors (visible in the browser’s console) or it was loading, but some of its functionality didn’t work. Thus, it’s best to leave those assets untouched as any optimization is completely irrelevant since the purpose of optimizing the website is mostly for the guest visitor and for Google PageSpeed Insights that accesses the website as a visitor.

However, some users, especially developers who work on various websites, are experiencing a slow load of Divi’s builder because there are too many plugins loaded on those WordPress websites, which also have lots of CSS/JS that could even interfere with the JavaScript files from Divi’s builder.

Asset CleanUp can be used to prevent specific plugins that are proven to be slow in loading and irrelevant to load on the page builder, in order to make the editor load faster (e.g. the whole editor could initialize in 2 seconds, rather than in 10 which would add up to the waiting time if it’s often used). This is recommended to be used only when the editor is really slow in loading and by those who really know what they are doing.

The following constant needs to be added to wp-config.php (note that it should be added BEFORE the line where “wp-settings.php” is required):

define('WPACU_LOAD_ON_DIVI_BUILDER_EDIT', true);

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

The moment this constant is set to true, some of Asset CleanUp’s rules will take effect on the builder which are the rules from “Plugins Manager” and the unload rules set within the CSS & JS manager for the targeted page, in our example /about-us/. In order to make sure the right RegEx rules are set in “Plugins Manager” if you want to unload entire plugins on the editor’s page, you have to make sure to include et_fb=1 in the RegEx. For instance, to match the URI /about-us/?et_fb=1&PageSpeed=off the following RegEx could be used: #/about-us/\?et_fb=1# (see the print screen below).

REMEMBER: You can also just use #\?et_fb=1# to match any page (not only “About Us”) that is having the Divi builder in use. It should work well in most situations.

If the editor has been working fine before and suddenly it stopped working after you enabled this option (placing that code snippet in wp-config.php), it means some of the unload rules are interfering with the Divi’s page builder and it’s better to deactivate it (remove the snippet) or if you’re keen to still have the editor load faster, then consult with a developer about it by checking the errors from the browser’s console.

Was this post helpful?