maxsteelz

Hi Saumya,

Thank you for your response.

Well the idea to use Cloudflare worker was to avoid seeing the swcf in the url also i plan to use this with Woocommerece. My understanding is that worker will work better compared to the page rule. Please correct/guide me in case i got this wrong.

Now coming to the Cache MISS/EXPIRED/DYNAMIC issue you have mentioned above – honestly, it is a normal thing – as Cloudflare will not keep items in the Cache if it does not have much traffic to it.

There is hardly any traffic on the website and it’s just me testing things. No wonder cache keeps getting expired. By the way before responding back i checked again to to confirm with Gtmetrix and again got a score of E with cache expired. At least now i know the reason that without much traffic CF is not serving it.

Smart tiered cache was already enabled. About cache reserve – it says apply for beta testing since i am on a free plan i guess this feature will not be applicable.However i have another option there ( Some new settings enabled by cloudflare beta testing) called cache rules and over there i have added a rule according to which if uri is a match then make it eligible for caching. Let’s see if this works similar to cache reserve and does the trick or not.

P.S.: Also do enable the option inside the plugin settings to add the proper cache control header for the static files: https://i.imgur.com/1oJeuXr.jpeg

This option i had enabled previously before posting here. So its been there all his while you tested.

Thank you once again for your prompt reply and support. I will let you know how it behaves with the new caching rule enabled. Honestly if a website is receiving less traffic not sure using Cloudlfare is a good idea? because it empties the cache defeating the whole purpose.

Thanks
max