The number in the admin bar menu does not indicate a % of work done, so it’s not supposed to go to 100% and there is no concept of “finishing” in Autoptimize.
Instead it is an indicator of the amount of disk space the Autoptimize cache is using (using 500MB as a threshold, but that’s somewhat arbirtrary).
If you delete AO’s cache, you also have to clear any page cache active (I think GoDaddy does page caching).
But “the paid version of Autoptimize” is new to me, as AO is not available in a premium version. What did you pay and where did you find information about it?
frank
Hi Frank and thank you for your response.
GoDaddy keeps calling it “paid plugin” in their correspondence so I assumed it was a premium version of the plugin – my error. I purchased a three-ticket support package from GoDaddy for around $60 and only used one ticket to optimize our site by consolidating the CSS and Javascript. GoDaddy chose the plugin and installed it as part of the purchased support.
Thank you for the clarification on the reading in the Admin bar. Just my opinion, because it does not reach 100%, it gives the impression it’s not finished. So, just to confirm, when the AO meter in the admin bar appears to no longer be growing in file size or the number of files, does that mean it is done optimizing?
The site is loading much faster. If, for whatever reason, I need to delete the AO cache again, I will remember to clear the page cache through GoDaddy as well.
Thank you Frank.
Shilo
So, just to confirm, when the AO meter in the admin bar appears to no longer be growing in file size or the number of files, does that mean it is done optimizing?
Autoptimize optimizes immediately, regardless of the % shown there. The only reason to keep an eye on that number is to make sure the cache isn’t growing too fast, it does not in any way indicate a % complete.
If, for whatever reason, I need to delete the AO cache again, I will remember to clear the page cache through GoDaddy as well.
that should indeed allow you to clear the cache without having to restore from backup 🙂
Thank you Frank.
you’re welcome, feel free to leave a review of the plugin and support here! 🙂
Hi Frank,
Can you please explain this? This is a result of the site crashing yesterday after deleting the cache in Autoptimize (as I explained above). I’ve cleared the site cache as you instructed using GoDaddy’s interface and this result has not changed.
https://blackrockmicro.com/ephys-newsroom/neuroscience-press-releases/
Thank you,
Shilo
I’m seeing PHP errors that complain about a problem with your theme actually;
Warning: Illegal string offset 'error' in /home/content/p3pnexwpnas05_data02/58/3206058/html/wp-content/themes/Jade/inc/template_single/post_preview_data.php on line 19
Warning: Cannot assign an empty string to a string offset in /home/content/p3pnexwpnas05_data02/58/3206058/html/wp-content/themes/Jade/inc/template_single/post_preview_data.php on line 19
Warning: Illegal string offset 'id' in /home/content/p3pnexwpnas05_data02/58/3206058/html/wp-content/themes/Jade/inc/template_single/post_preview_data.php on line 20
When busting the cache (https://blackrockmicro.com/ephys-newsroom/neuroscience-press-releases/?bust_cache=randomstringheretobustcache) to bypass the page cache those errors don’t show.
In that case I suggest you:
* clear the page cache again (as it seems the page with the PHP errors have been cached)
* contact the theme author with those error messages
hope this helps,
frank
Yes, and GoDaddy resolved that saying the debug mode had been turned on in the Wp-config file and the site was being cached. He changed the debug mode to false and and forced the cache to clear. The errors went away. GoDaddy Rep said the errors were appearing because after the AO cache was deleted, GoDaddy cached the site right after the errors started to appear.
Everything seems to be working fine now. Thank you for all the clarification.
He changed the debug mode to false and and forced the cache to clear.
that should indeed help 🙂
