This feature is available in the Pro version starting from v1.2.6.2 (it’s relevant only for those that want to unload any plugins within specific pages from the Dashboard). Feature Overview This option is located in “Plugins Manager” — “IN THE DASHBOARD /wp-admin/” tab (if the unloading plugins in the Dashboard is an enabled option) and […]
Category: Unload Rules
How to unload or only load whole plugins if the logged-in user has a certain role?
This feature is available in the Pro version starting from v1.2.3.8. There are situations when you might want to unload specific plugins in the front-end view if the logged-in visitor has a certain role (e.g. administrator, subscriber, editor, etc.). Some plugins might unload unnecessary CSS/JS files for the ‘administrator’ role, but necessary for the ‘subscriber’ […]
How to unload or only load whole plugins on all pages of Search, Date, Author post type archives?
This feature is available in the Pro version starting from v1.2.3.5. WordPress comes with built-in pages such as search results, list of posts/articles that are published on a specific date or belong to a specific author. Many WordPress websites have themes that are using the built-in search page. If there are many articles posted there […]
How to unload or only load whole plugins on all pages belonging to specific post types?
Many public pages in WordPress can be posts (e.g. the articles from the blog), pages (e.g. contact, about, terms), or custom post type pages such as the WooCommerce product pages which belong to the “product” post type. Sometimes, there are plugins that are loaded in these kind of pages, but they are not needed and […]
How to unload or only load whole plugins on all pages that have certain taxonomies (category, tag, etc.) set?
This feature is available in the Pro version starting from v1.2.3.4. This option is useful if you want to unload or load as an exception (from any unload rule already set) whole plugins on taxonomy pages. These include the built-in categories (“category”), tags (“post_tag”) and custom taxonomies which includes the popular WooCommerce product categories & […]
Is Asset CleanUp Pro loading when REST API calls are made? Can I unload plugins to make the calls faster?
Note: This option is available in the Pro version starting from v1.2.2.0. By default, Asset CleanUp Pro is disabled whenever a REST API call is made. As there is no front-end to optimize in this situation (e.g. nothing to alter on the HTML source code), it’s better to avoid triggering the code from the plugin […]
Is Asset CleanUp loading when Bricks Visual Site Builder is used? How to make the editor faster?
Note: This option is available in the Pro version 1.2.1.7. By default, Asset CleanUp Lite/Pro does not trigger when Bricks Visual Site Builder is used, more precisely when the following query string is in use: bricks=run. For instance, you might have an “About Us” page and it’s built using the “Bricks Visual Site Builder” theme. […]
How to unload or only load CSS/JS assets on all pages that have certain taxonomies (category, tag, etc.) set?
This feature is available in the Pro version starting from v1.2.0.5. This option is useful if you want to unload CSS/JS on specific post pages of any kind including, but not limited to: posts (their default well-known taxonomies are “Categories” and “Tags”), pages, custom post types such as WooCommerce’s “product” (it has “Product categories” and […]
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, […]
Is Asset CleanUp loading when Oxygen’s Visual Site Builder is used? How to make the editor faster?
By default, Asset CleanUp Lite/Pro does not trigger when Oxygen’s Visual Builder is on, more precisely when the following query string is in use: ct_builder=true. For instance, you might have an “About Us” page and it’s built using Oxygen. The page builder can be accessed in the front-end via /about-us/?ct_builder=true. While you use the visual […]