apparent conflict with WP Super Cache
-
Thanks for your plugin
i’ve installed on a WP multisite, activated on one subsite, also have WP Super Cache and Autoptimize
just want to unload scripts from homepage.
in Asset Cleanup settings it looked like your plugin recognized Autoptimize – I left all settings as default
in page editor manually unloaded the scripts and it looked to work great, reduced number of scripts by a lot
thought all was good… until…
I ran various sites through GTMetrix expecting joy at even faster load times… but no…
time to first byte slowed down by over one second. happening on all sites even without Asset cleanup activated
deactivate Asset Cleanup, and deleted WP Super Cache and things returned to normal.
When deleting WP Super Cache cache (before deactivating asset cleanup) it prompted a message that the advanced-cache.php file in wp-content had to be manually deleted (I’ve never seen that before).
not sure how to proceed, by default are all Asset Cleanup settings disabled or does it do some caching function simply by being activated?
Regards.
-
@wasanajones you can leave Asset CleanUp settings as default since you’re using Autoptimize and using Minify/Combine is deactivated in Asset CleanUp if already used in Autoptimize.
From my experience having time to first byte going up by one second is very likely because of a non-cached version of the page that was read by GTMetrix.
I find it really odd/surprising that deactivating WP Super Cache and Asset CleanUp returned things to normal. Perhaps you’re using a hosting caching system (e.g. from WP Engine, Kinsta, etc.) and using WP Super Cache does not bring extra benefits at least when it comes to just caching pages?
Asset CleanUp doesn’t alter in any way, nor reads anything from advanced-cache.php as the plugin is a front-end optimization plugin, not a caching plugin. WP Super Cache, just like other caching plugins, should take the HTML Source (with the CSS/JS unloaded from Asset CleanUp, not printing at all in the final HTML output) and create the HTML static versions that should be read instantly when accessing the page via Incognito or GTMetrix. The only thing Asset CleanUp does which is related to “wp-content” directory is writing the minified/combine versions of CSS/JS to /wp-content/cache/asset-cleanup/ if you have the options enabled. From what you mentioned, you’re already using Autoptimize for this anyway.
I suppose no query strings were used when you made tests as caching plugins usually don’t cache pages with extra queries in the URL (e.g. /page-slug-here/?param=value_here)!?
One more thing: If Asset CleanUp is deactivated, it will be like not having it active in the first place. It doesn’t leave any traces of any kind that would interfere with any caching system (either a plugin or the hosting one). It will keep its settings in the database (unless you use “Tools” -> “Reset” and clear them) and the cached CSS/JS from /wp-content/cache/asset-cleanup/ in case you will reactivate it (some people make tests and activate/deactivate the plugin often and they need to have their settings preserved. Or, they upgrade to the Pro version and, of course, they don’t want to apply all the unload rules again).
The topic ‘apparent conflict with WP Super Cache’ is closed to new replies.
