Asset CleanUp Pro - Best Performance WordPress Plugin

Asset CleanUp Pro - Best Performance WordPress Plugin v1.2.6.7

No permission to download
Download Asset CleanUp Pro v1.1.8.6 - Performance WordPress Plugin Nulled Free
= v1.1.8.6 - 4 January 2021 - Thank To @TassieNZ

* New Feature: Unload plugins within the Dashboard /wp-admin/ (useful for pages that are too slow and, in rare cases, to fix any conflicts between two plugins loaded on the same admin page)
* Fix: Inline CSS for specified files was not working anymore if the CSS file was cached
* Added option to prevent CSS/JS from being optimized on page load by Asset CleanUp Pro via query string for debugging purposes: (/?wpacu_no_optimize_css /?wpacu_no_inline_css /?wpacu_no_optimize_js)
Download Asset CleanUp Pro v1.1.8.5 - Performance WordPress Plugin Nulled Free
= v1.1.8.5 - 18 December 2020

* Replaced jQuery deprecated code with a new one (e.g. reported by "Enable jQuery Migrate Helper" plugin)
* Download file based on the browser's screen size feature addition: Show the option also for CSS files that are "parents" and have "children" under them, alerting the admin to be careful when a rule is set for the file as it could affect the way its "children" are loaded
* Debugging option: If the admin uses /?wpacu_only_load_plugins=[list_here_comma_separated] while he/she's logged-in, then Asset CleanUp's MU plugin file will only load the mentioned plugins (all the other active plugins will not load at all on the targeted page)
Download Asset CleanUp Pro v1.1.8.4 - Performance WordPress Plugin Nulled Free
= v1.1.8.4 - 1 December 2020

* New Setting: Restrict access for administrators on the "CSS & JS Manager" area, thus decluttering the posts/pages whenever they edit them; Very useful if there are admins (e.g. store managers that don't have to mix with Asset CleanUp's assets list for various reasons) that should not view the the meta boxes from edit post/page, the CSS/JS list from the front-end view (if enabled), etc.
* Improvement: Extra checks are made to detect if the page is an AMP one and if it is, no changes would be made to the HTML source (e.g. no SCRIPT tags in the HEAD section of the page)
Download Asset CleanUp Pro v1.1.8.3 - Performance WordPress Plugin Nulled Free
== Changelog == Thanks To @TassieNZ
= v1.1.8.3 - 22 November 2020

* Changed the "Plugins Manager" area to have the same feeling as the "CSS & JS Manager"; Removed the "Always load it (default)" option as it's redundant, since all the plugins are loaded by default unless there are unload rules set there; The load exceptions are now showing in green font to stand out in case they overwrite any unload rule.
* Added extra alters to notify the admin in case something is not right with some of the rules set. These include: adding the full URl to the RegEx input areas when only the URI (relative path) is needed; Enabling both "Unload it if the user is logged in" and "Always load it if the user is logged in" which ends up in the cancellation of each other
* Added "Unload it if the user is logged in" option to "Plugins Manager" (e.g. sometimes, you have a plugins that has Google Analytics and you want to trigger it only for your guests, not for yourself)
* Added debugging option to load all plugins (no filtered list in case there are any rules in "Plugins Manager"): /?wpacu_no_plugin_unload
* Make sure all the "if kept loaded" areas are blurred if any unload rule is chosen as those areas become irrelevant
* New option in "Settings" -> "Combine loaded JS (JavaScript) into fewer files" -> "Wrap each JavaScript file included in the combined group in its own try {} catch(e) {} statement in case it has an error and it would affect the execution of the other included files"
* Clear caching once a day via WP cron in case over 24 hours have passed since last clearance (e.g. in case the admin hasn't cleared the caching in a long time or hasn't touched the Dashboard for days)
* Deactivate the appending of the inline CSS/JS code (extra, before or after) to the combined CSS/JS files if all the files' size is over 700 MB as this often suggest the inline code is not unique (e.g. having WordPress nonces that often change)
* Check if a directory is empty before using rmdir() to avoid certain debugging plugins to report errors (even though they are harmless)
* Make sure the following work fine if the plugin is marked as unloaded site-wide with exceptions: upload file within the front-end, download attachments from the Dashboard
* Fix: Basic preloading was not taking place anymore
* Fix: "PHP Warning: in_array() expects parameter 2 to be array, boolean given" is generating if the current media query load list is empty
* Fix: Make sure /wp-content/cache/asset-cleanup/(css|js) directories are re-created if necessary, in case they were removed (e.g. for being empty or by mistake)
* Fix: The list of the hardcoded assets wasn't wrapped correctly and not contracted properly on request
* Fix: The AJAX call meant for fetching the hardcoded list in the front-end view was also triggering within the Dashboard outside the plugin's pages and used extra resources that were not necessary
* Fix: Prevent the meta boxes from showing up in the edit post/page area (thus, decluttering the edit area) if the user's role is not "administrator" (e.g. it was showing it to editors without any CSS/JS to manage which was often confusing)
Download Asset CleanUp Pro v1.1.8.2 - Performance WordPress Plugin Nulled Free
v1.1.8.2 - 16 October 2020 - Thanks To @NullMaster

* New Feature: Instruct the browser to download a CSS/JS file only when a certain media query matches (e.g. you might have a certain CSS file that is needed only in the desktop view, but not on mobile view)
* Prevent the plugin from triggering when Lumise plugin is used in edit mode
* Improvement: In the front-end view (when "Manage in the front-end" is enabled), the hardcoded assets are retrieved via an AJAX call for higher accuracy especially when certain plugins are using various techniques to list their assets (e.g. "Smart Slider 3")
* Oxygen Builder Fix: Make sure the file /wp-content/uploads/css/universal.css is taken into consideration for minification as it's among the files that aren't minified by default
Download Asset CleanUp Pro v1.1.8.1 - Performance WordPress Plugin Nulled Free
= v1.1.8.1 - 29 September 2020

* Combine Google Fonts: The plugin checks if the option is enabled before using specific functions related to it, thus reducing the usage of more resources (on some shared hosting packages, the page returned 503 error)
* Combine JS: Skip adding inline JS with WordPress Nonces as they are not unique and add up to the disk space (better accuracy in detecting them)
* Added notification to the plugin's top right area if "Test Mode" is enabled (for extra awareness)
* Fix: In some environments, the plugin's custom functions to detect if the user is logged-in were triggering errors
* Fix: Do not alter the "ver" value to the default WordPress version (as it used to be) as some scripts should be loaded without query strings especially if "ver" was set to null on purpose
Download Asset CleanUp Pro v1.1.8.0 - Performance WordPress Plugin Nulled Free
1.1.8.0 - 21 September 2020

* Made sure a directory exists before attempting to delete it (for old directories) to avoid any error reports (harmless, but annoying) from plugins such as "Fatal Error Notify Pro"
* Updated notification related to HTTP/2 from Combine CSS/JS tabs within "Settings"
* If the total files from the caching directory generated by the combined CSS/JS files occupy over 1 GB in disk space, deactivate automatically the appending of the inline CSS/JS code associated with the tags to the generated combined CSS/JS files as that's usually the culprit for having so many redundant files in the caching directory, leading to unnecessary disk space
* Older caching files are by default set to be cleared after 4 days (the new default value) instead of 7
* Updated "Help" page
* Show more information about the caching directory in "Tools" -> "Storage Info" (each directory with CSS/JS files is shown along with the total size of the assets within it)
* WP Rocket 3.7+ compatibility fix: "Minify HTML" is removed (read more: https://github.com/wp-media/wp-rocket/issues/2682), thus, make sure this gets verified (for compatibility reasons) as well in Asset CleanUp Pro
* Shorten the file name of the combined CSS/JS to avoid possible duplicates
* Fix possible errors (400 Bad Request) when AJAX calls are made by Asset CleanUp Pro
* Check if Cloudflare is used and notify the user about whether it's needed to enable "CDN: Rewrite assets URLs" (read more: https://assetcleanup.com/docs/?p=957)
  • Like
Reactions: shaunp and NBB
Download Asset CleanUp Pro v1.1.7.9 - Performance WordPress Plugin Nulled Free
v1.1.7.9 - 5 September 2020

* Improvement: Save resources and do not check anything for optimization when the feed URL (e.g. /feed/) is loaded (the plugin should be inactive for these kind of requests)
* Improvement: Do not trigger the plugin when WooCommerce makes AJAX calls (no point in using extra resources from Asset CleanUp)
* Improvement: When Google Fonts are marked for removal, nullify other related settings, leading to the usage of fewer resources
* The strings "/cart/" and "/checkout/" are added to the exclusion list where Asset CleanUp Pro is not triggered if the pattern is matched (read more: https://assetcleanup.com/docs/?p=488); These kind of pages usually do not need optimization and if the admin decides to do some, he/she can remove the exclusion
* Fix (writing files to caching directory): If the handle name contained forward slash (/), make sure that the final file name gets sanitized (including slash removal) to avoid errors related to file_put_contents() such as trying to write to directories that are non existent
* Fix (unnecessary cached files): The plugin was caching CSS/JS files that did not need to be cached (e.g. already minified JS), leading to unnecessary extra disk space
* The Pro version won't deactivate the Lite one automatically (if it's enabled) as it can be kept active for full compatibility with plugins such as "WP Cloudflare Super Page Cache"
* "WP-Optimize" minify is not triggering anymore when /?wpacu_clean_load is used for debugging purposes
* Do not strip inline CSS/JS associated with the handle if the original file is empty as there's a high chance the inline code is needed
Download Asset CleanUp Pro v1.1.7.8 - Performance WordPress Plugin Nulled Free
v1.1.7.8 - 27 August 2020

* CSS/JS unloading and other optimization options are now available for `Custom Post Type Archive Pages` (not just the singular pages belonging to the custom post type)
* Fix: Sometimes, "Fatal error: Cannot use object of type WP_Error as array" PHP error is logged when the assets are retrieved via "WP Remote Post"
  • Like
Reactions: shaunp
Download Asset CleanUp Pro v1.1.7.7 - Performance WordPress Plugin Nulled Free
= v1.1.7.7 - 19 August 2020

  • Make the plugin's user aware about jQuery Migrate not loading starting from WordPress 5.5 (a notice is showing in "Settings" -> "Site-Wide Common Unloads" if the WP version >= 5.5)
  • Add alerts for WooCommerce assets when the user is about to unload them to make sure he/she is aware of the consequences (e.g. "js-cookie", "wc-cart-fragments")
  • Oxygen plugin compatibility: Make sure the page loads fine when "Manage in the front-end view" is enabled and the admin is logged-in (e.g. ob_flush() is used to print missing content)
  • Do not unload plugins (any unload rule from the "Plugins Manager" area) on front-end pages if an AJAX request was made (e.g. some plugins such as WooCommerce & Gravity Forms are using index.php?[query_string_here] and we won't want to block these calls as they are obviously made for a reason)
  • Added action hooks before ("wpacu_clear_cache_before") & after ("wpacu_clear_cache_after") the plugin's CSS/JS caching is cleared
  • Do not deactivate the plugin automatically on Dashboard view if the PHP version is below 5.6 and when the plugin is activated, prevent its activation when the PHP version is below 5.6 printing an error message
  • Yoast SEO Compatibility Fix: Prevent the plugin from minifying SCRIPT tags if the type is different than "text/javascript", avoiding errors with plugins such as Yoast SEO (type: application/ld+json)
  • WordPress 5.5 & "Enable jQuery Migrate Helper" Fix - /assets/script.min.js: jQuery.fn.load() is deprecated
  • When the CSS/JS list is fetched using the "Direct" way of fetching the assets ("Manage in the Dashboard"), there are two calls made; Now the progress is shown for each of the calls for easier debugging in case the assets' list is not retrieved successfully
  • Improvement: Do not defer the plugin's own script file as sometimes its functions do not work (e.g. if there are JS errors from other plugins); It's better to have it loaded as render-blocking (small file anyway), as soon as possible
  • Improvement: Do not leave extra space in the LINK & SCRIPT tags (it makes things easier when debugging the HTML source that might have been altered by the plugin)
  • Fix: Avoid triggering the plugin if the request is an API one starting with "/wp-json/wc/" (excluding the site's base URL), WooCommerce related (REST requests)
  • Fix: PHP Notice: Array to string conversion (CombineCss.php on line 503)
  • Fix: PHP Notice: Undefined index: is_frontend_view (view-by-location.php on line 311)
  • Fix: Fix: When assets are fetched, the list of CSS/JS wasn't showing up (AJAX call error) if the page URL that is called (from which the assets are fetched) is loaded with HTTP protocol while the Dashboard (the URL from which the AJAX call is made) is accessed via the HTTPS protocol - Error: "This request has been blocked; the content must be served over HTTPS."
  • Fix: "PHP Warning: Use of undefined constant CURL_HTTP_VERSION_2_0" (triggered only for the admin to check if the server supports the HTTP/2 protocol); Show the verify link for HTTP/2 protocol if the automatic detection is not working
  • Fix: "PHP Notice: Undefined variable: pluginListContracted in (…)/templates/meta-box-loaded-assets/view-by-location.php"
  • Security Fix: Sanitize values from BulkChanges.php to prevent the execution of arbitrary code (e.g. JavaScript code)
  • Like
Reactions: NBB

About us

  • Our community has been around for many years and pride ourselves on offering unbiased, critical discussion among people of all different backgrounds. We are working every day to make sure our community is one of the best.

Quick Navigation

User Menu