sdawales

I don’t have it excluded in AO and I never had the issue before. Not sure if this is a potential reason but the blocking is jquery 3.5.0 and the update was up to 3.5.1. Wonder if they forgot to change version numbers somewhere? Anyway, it looks like you are saying that its nothing to do with AO so I’ll go bug someone else about it. Thank you as always.

I also sent Yoast a message and got the following reply from Patrick which was much appreciated. I thought I would post it here since someone else may stumble across this;

hentry is one type of microdata format (schema is another type). We are not sure if the hentry microdata format has been depreciated by all Search Engines or just Google or even if it is still in use. We can only say to contact Google for more information. You may contact Google by making a post on their forums: https://productforums.google.com/forum/#!forum/webmasters.

We do know that Yoast does not output that microdata format. Instead, Yoast outputs schema. This guide explains more about the schema we output: https://developer.yoast.com/features/schema/plugins/yoast-seo

Hey Frank, when you say AO cannot lazyload background-images (yet). What kind of timeframe is (yet)? ??

We were trying to lazy load background images and AFAIK, jquery needs an additional plugin to make this happen and he was loading it from cloudfare. So like I said, it had nothing to do with this fantastic plugin although I still can’t lazy these damn background-image:url. ?? Thank you all the same.

Nothing to do with jquery updater. Sorry.

Converting woff to woff2 also helps. I just went through this and it does make a sizeable difference.

Correct. But I want to have the cache minification active on Cache Enabler and not AO. That I can do easily but my problem is that my newly cached pages do not respond with a service worker. That is the problem.

Frank, If I clear the jobs in AO CCSS, would that by chance also clear the ao_ccss_queue in cron? It appears that it has happened to me since I cleared them and then they were stuck again as “N”. I looked in cron and ao_ccss_queue is missing. Thanks.

Yes and thank you.

Now I am using AO2.7.0, can I go ahead and remove the old Autoptimize CriticalCSS.com plugin? I’m all good with 2.7. Thanks

Thanks Daan. One last thing. Cache policy for super stealth. Can it be cached as normal?

OK. Thanks Daan.One last thing and it is probably a silly observation but the name super-stealth implies something nefarious. I doubt many users would ever see that reference but… BTW, great plugin and I cant wait to write a review.

• This reply was modified 4 years, 7 months ago by sdawales.

Got it. Unfortunately, installing the super stealth upgrade just gave me a fatal error so I can’t do a thing at the moment. Site is 100% down ??

Yes I did save and then update analytics.js. The exact url called is; Thanks.

https://www.google-analytics.com/collect?v=1&_v=j81&a=1697960580&t=pageview&_s=1&dl=https%3A%2F%2Fwww.pressertech.com%2F&ul=en-us&de=UTF-8&dt=Mercedes%20Tuning%20%E2%80%93%20Mercedes%20Tuners%20%E2%80%93%20Chiptuning%20Mercedes%20%E2%80%93%20Mercedes%20Benz%20Tuning%20-%20Pressertech%20Performance&sd=24-bit&sr=1920×1200&vp=1009×652&je=0&_u=YEBAAAAB~&cid=2089801725.1587395706&tid=UA-115495923-1&_gid=1542442873.1587395706&z=605395967

Thanks Daan. I did enable stealth and flushed my cache but it’s still there. I’ll have to have a play with it. Regarding the Super Stealth plugin, I am open to support the plugins that work and I use every day. How much weight does it add to a page? No compatibility issues with the likes of autoptimize? Thanks in advance.