davidgeipel

Thanks Lisa. The odd thing was that LiteSpeed was working with it checked. Must be that LS didn’t see the file from W3TC – “this file is detected as belonging to another plugin, LiteSpeed Cache will not cache”

It’s hard to tell if it does precache those sitemap pages – I don’t see anything in the header for our sitemap page either. Hmmmm.

Anyway, still hopeful your product team can find a way to offer a light weight version of the crawler. I know I am on shared hosting but I would think they would allow a lite version (limited to say 100 pages) because otherwise WP Rocket or W3TC would chew up more server resources. Hope you can keep those other posts alive internally and push to the top. Same with a special AMP cache.

Dave

I thought they would have addressed this in the latest update two days ago. NOPE.

Proceed with caution: A currently active plugin, Wordfence Security may be incompatible with A2 Optimized.

Also, why haven’t they enabled or integrated with Litespeed cache. My preferred caching anyways. IF you have their turbo plan, this is ideal. Anyone not using that plan would quickly upgrade because Litespeed cache is unreal – just trying to get some extra benefits from this app like memcache but the A2 plus W3TC plus LS Cache requires too much fine tuning for my liking. A constant warning too since Wordfence is running is also the final straw. So frustrating.

Dave

We’ve seen it too for years. Any other suggestions?

Hope company support can respond.

Pingdom shows the actual waterfall – and Tawk is always next to last.

Thanks Hai. I think if you asked, there would be a lot of interest from those using it – because you need to have it to get better ranking on google. It’s the next main push this past year apart from SSLs that they’re looking at in addition to speed.

LiteSpeed + AMP = super punch!