Marko Vasiljevic

Hello Stien,

I am sorry about the issue you are experiencing and I’m happy to assist you with this.
We’ve also received the email via the support channel, and I asked you some follow-up questions. We can continue the correspondence there since you are a Pro user.
IS REST API cache enabled in Perfomrance>Page Cache>REST API?
I can see that you’ve set up Full site delivery, however, you are also using the CDN with the URL rewrite, so in this case, you should disable the CDN in Performance>General settings and only use FSD CDN.
The pages are cached once visited. So if you wish to preload the pages you can use Cache Preload in Performance>Page cache and Automatically prime the page cache. There you will also see the option Preload the post cache upon publish events which does exactly that. since the Cache Preload is triggered by the page view and sometimes wp cron is not very reliable, I would advise using the default settings in Cache Preload and possibly set a custom cronjob for page visit on your server, for example, every 5-10 mins or better yet use wp-cli.
Logging is available in wp cli so instead of calling wp cron via crontab – you should call it directly via
wp w3-total-cache pgcache_prime
and track the output which pages / sitemap positions are primed by script.
Thanks!

Hello KLC,

I can see that you are using Cloudflare and Autoptimize, however, I do not see traces of W3 Total Cache.
If you are using W3 Total Cache, make sure that Minify is disabled since you are also using AO and Cloudflare. Also, make sure that Cloudflare Minify is disabled since AO is handling this.
NOw when it comes to Google Page speed suggestions, They are related to the plugin you are using to Minify the assets, so in order to eliminate render-blocking resources, you need to address this to Autoptimize support.
Removing unused JS/CSS cannot be done by any plugin. This is because the theme you are using and the plugins you are using are loading js/CSS files on all pages and not just the pages intended.
Also, you might want to pay a bit more and use Stackpath Full site delivery instead of the Cloudflare free plan. I’ve also found this article which may help you with the configuration.
Thanks!

Hello Mike,
Thank you for your question and I am happy to assist you with this.
As I’ve already replied in wp.org topic, we cannot troubleshoot if we don’t see the problem.
Can you please share the Performance>Minify settings (a screenshot would be great) and check the nginx cond if it contains necessary rules provided in Perfomrance>Install.
And please let me know where you wish to continue the correspondence so we can avoid duplicating the answers.
Thanks!

Hello Carolee,

You can use User Agent Groups for this. In Performance>Cache Groups>Manage User Agent Groups, you can specify the group of user agents by specifying names in the user agents field. Assign a set of user agents to use a specific theme, redirect them to another domain or if an existing mobile plugin is active, create user agent groups to ensure that a unique cache is created for each user agent group. Drag and drop groups into order (if needed) to determine their priority (top -> down).
So in your case, enable the group, select pass-through in the Theme drop-down, and add the URL in Redirect users to: field that is required by the redirect plugin.
Make sure to save all settings and purge the cache after the changes are made
I hope this helps!
Thanks!

Hello Nicola,

Thank you for providing the info and detailed explanation.
Let me test this and get back to you to see if I can replicate this and if the provided code works without any issues.
Once again thank you for provided details and your patience.

Hello Nicola,

I am sorry about the issue you are experiencing with clearing the w3tc_minify option from the database.
I need to check this and try to replicate and I’ll get back to you as soon as investigate this more.
Thank you for your patience.

Hello Dominique

Thank you for the information.
It seems that jquery-migrate is necessary and custom.unified.js?ver=4.8.1:51 is dependable on it so you should keep that option disabled.
I am glad to know the issue is resolved!
Thanks!

Hello Chris,

Thank you for the information provided.
As I’ve already answered you in wp.org and this a duplicate post please make sure to check the wp.org topic:
https://wordpress.org/support/topic/prevent-caching-with-gravityforms/#post-13868293

For your convenience this was my reply:

You should use the correct groups and each group should specify {key}={value}
Depending on what key you are using, that should look like {key}='{“strict”:”1″,”thirdparty”:”0″,”advanced”:”0″}’
So you should replace {key} with the actual cookie name.

And don’t forget to enable all the checkboxes (enable and cache)
Once again as the cookies are cached and may change depending on a value, you should exclude those pages from being cached to avoid this.
This is simply how cache works. I hope this helps!
Thanks!

Hello Svyatoslav,
Thank you for your inquiry about the caching statistics feature.
The improved Statistics page allows you to check the Hit rates and overall effectiveness of every configuration enabled in your General settings.
You can use Statistics to check the following:

• Page Cache (Disk, Disk-Enhanced, Redis, Memcached)
• Minify
• Object Caching
• Database Caching
• Fragment Cache
• System info (PHP Memory, CPU Info)
• Cache storage size used (Redis, Memcached)

Enabling the Debug mode for each setting in Performance > General Settings > Debug gives you more detailed information by clicking on a link of the desired setting in the Statistics Page.
If for example, Object Cache is disabled, it won’t be available in Statistics
In Performance > General Settings > Statistics, you can enable Statistics and customize your desired settings.
Please check this screenshot
You can check more detailed information in our documentation.
Thanks!

Hello Michael,

Thank you for the clarification.

In this case, you can use W3 Total Cache for caching. However, once the user is logged in if the option in W3 Total Cache “Don’t cache pages for logged in users” is enabled, then the user will not receive cached pages. In case you want a logged in users to see cached pages, you should disable that option.

Again it’s not recommended to serve cached pages to logged-in users.

If you by any chance run into any kind of issue, please make sure to drop us a note so we can assist you with this.

Thanks!