Autoptimize breaking several plugins and my theme

your site seems down currently Orlando (503 error)?

frank

Yes ?? I’ve just noticed. I’ll let you know when it is up again. ??

It’s up again.

Thanks in advance.

OK, I think that this is what’s happening;
* you’re using Gutenberg
* the relevant JS-files are downloaded from https://c0.wp.com/c/5.0.3/ (probably Jetpack doing some magic) so they are not (and cannot) be aggregated by AO
* you’re “also aggregating inline JS” as a result of which the variable used by some of the Gutenberg files are not there when the Gutenberg files are loaded

So start with disabling “also aggregate inline JS” maybe and test what works and what doesn’t, all the while keeping an eye on the browser console for JS errors?

Ok, it worked…for a while. Right now, I’m experiencing a weird problem: I can’t delete cache, not from the admin bar, and not from the settings page. I don’t see any errors on logs, I’ve tried reinstalling and nothing. And I don’t know why, but that same cache regenerates every time, even if I delete it manually.

I did some tests with Fast Velocity Minify and ShortPixel Adaptive Images, and somehow something broke. Also tested Async Javascript.

Right now AO is enabled, but console shows a ton of errors.

Can you please help me?

Also, I disabled the common JS CDN feature of JetPack.

And I don’t know why, but that same cache regenerates every time, even if I delete it manually.

well, AO will “warm up” the cache after purging to speed things up, maybe that’s what you’re seeing?

Right now AO is enabled, but console shows a ton of errors.

I’ll have a look ??

wow, you (or one or more plugins) are loading almost all of gutenberg (including react and react-dom and lodash and …) on your frontend and you have inline JS that depends on those files being loaded, causing the console errors.

3 potential solutions;
* exclude wp-includes/js/dist from JS optimization
* OR tick the “also aggregate inline JS”-option (keep an eye on cache size in that case though)
* OR somehow stop all those Gutenberg-files from being loaded on your frontend in the first place, it’s horrible for performance; you’re pushing almost 3MB of JS to your visitors this way and I see no reason why really ??

hope this helps,
frank

well, AO will “warm up” the cache after purging to speed things up, maybe that’s what you’re seeing?

I always see 94 files on cache information after purging the cache, and I’m positive before this issues I remember they were zero. Today they were like 124 or something like that, after purging the cache they were 94 again. ??

that does not have to indicate a problem really … have a look in wp-content/cache/autoptimize/js and wp-content/cache/autoptimize/css and check;
* how many files are in each?
* how many of those files are autoptimize_snippet* ?
* how many of those files are are autoptimize_single* ?

* OR tick the “also aggregate inline JS”-option (keep an eye on cache size in that case though)

Ok, that solved it.

OR somehow stop all those Gutenberg-files from being loaded on your frontend in the first place, it’s horrible for performance; you’re pushing almost 3MB of JS to your visitors this way and I see no reason why really

I think I found the culprit…it’s a plugin called Advanced Rich Text Tools for Gutenberg, it enqueues a lot of things without checking whether is loading on the front or in the admin. Now GTmetrix is reporting 541KB page size, down from 1.3MB. ??

Everything is working again.

Thank you very much.

I think I found the culprit…it’s a plugin called Advanced Rich Text Tools for Gutenberg, it enqueues a lot of things without checking whether is loading on the front or in the admin.

yeah, doing Gutenberg the correct way is the next challenge for plugins ??

Everything is working again. Thank you very much.

you’re welcome Orlando, feel free to leave a review of the plugin and support here! ??