Caching settings for Core Vitals improvements with Litespeed

Great to hear you’re looking to make the most of your AMP site. To answer your questions see below:

1. Litespeed has an option to “cache mobile” – which says: “Cache mobile views separately. Only enable for AMP or mobile-specific design/content, not for responsive sites.” Since the site is fully AMP…. should this be on or off?

From checking up on this has configuration this seems to be user preference, not specific to AMP URLs. I suspect AMP is mentioned here as many users initially used AMP for mobile URLs, before the plugin offered transitional and standard modes. You can check with the plugin developer for any queries on this although, I don’t think it’s AMP specific.

2. Any advice for the best way to optimise all the AMP scripts? I know there is a running issue and thread on Github about this, but wondering it there is something that can be done in the interim to improve results?

The scripts are already optimized for best performance. Other users have suggested merging scripts with one such discussion found here.

Note that if you’re finding the scripts listed as an opportunity within PageSpeed Insights there’s an open GitHub issue in relation to this which you may already be aware of.

While the plugin implements most of optimizations already you can also use the AMP Page Experience guide for further opportunities.

1. Litespeed has an option to “cache mobile” – which says: “Cache mobile views separately. Only enable for AMP or mobile-specific design/content, not for responsive sites.” Since the site is fully AMP…. should this be on or off?

This would not be relevant on your site since you are using Standard mode. It would only be relevant if using Transitional or Reader mode and you have mobile redirection enabled and you’ve turned off client-side redirection (via a PHP filter).

Great, thanks guys! I suspected that’d be the case re AMP and having it off, thanks for confirming.