Hi @peterdowney01,
I saw a bunch of issues on your website so I’m pointing them out here, hopefully once you implement them all your issues will go away.
But before I get onto the issues, I would like to let you know that when using the Worker mode, when a cache is MISS it shows as DYNAMIC, I know it’s wired but that’s what it happens. That is why when using worker mode you should look at x-wp-cf-super-cache-worker-status header value in the response header. you will see that when CF cache status is DYNAMIC that header value is MISS. Hope this clarifies the dynamic things.
Screenshot: https://i.imgur.com/OdqjV5v.jpeg
View post on imgur.com
Now coming to the issues:
1. Looking at the response header of your website I can see that you are using both this plugin + Cloudflare APO and Cloudflare official plugin. Please don’t do that. When using this plugin you cannot use CF APO or the official CF plugin. You need to choose one or the other. If you choose to use APO then use APO + official CF plugin otherwise you need to deactivate API in your CF dashbaord and also remove the official Cloudflare plugin from your website and only use this plugin.
Screenshot: https://i.imgur.com/sF2wKzR.jpeg
2. Why are you using the worker mode? Is there any special reason behind it? Have you checked the new cache rule based implementation guides released with the current version of the plugin: https://gist.github.com/isaumya/af10e4855ac83156cc210b7148135fa2
Basicallly you can use the Cache Everyything page rule without worrying about the ?swcfpc=1 cache buster query string. If you haven’t checked it out, in the plugin settings > Other tab and scroll down on that page you will see the option.
Make sure you read the implementation guide first and implement the rules properly before enabling that option.
3. Super charging the cookir bypass: https://i.imgur.com/w8rhrLx.jpeg
Do you really need to enter bookly_?|comment_|(c(_|wid)|dd_)|jetpack|no_?cache|woocommerce_(cart_hash|items_in_cart|recently_viewed)|wordpress_|wp(-|sc_)|xf_|yith_w(cwl_session|rvp) in the custom cookie bypass section? I honestly don’t think so.
With the default setup the plugin comes with it automatically bypass cache for most cookies, you you never ever have to use that option. What you have added there is really useless and is absoluetely not needed.
Once you work on these suggestions, you will see great results. I will also recommend you to enable the Smart Tiered Cache in your Cloudflare dashhboard.
