Workers doesn’t seem to be working

On the Workers page, I clicked on the preview and see a message to follow

– I don’t understand what you mean. If you want to use this plugin, first of all, you need to remove the official CF plugin from your site as you cannot use both plugin at the same time. Also disable APO inside the CF dashboard.

Then inside this plugin settings, under Cache tab enable the worker mode. And then click on Enable Page caching. That will automatically add the worker code needed for the caching to your CF account.

There is nothing to preview here on the workers page.

thank you @isaumya yes, the official plugin I had already disabled. But I didn’t know that I needed to deactivate APO on Cloudflare panel. Now it looks like it worked!

another questions:

1) to satisfact Core Web Vitals warning “Serve static assets with an efficient cache policy” I selected “Browser Cache TTL = 1 year” on Cloudflare panel. This disrupts the plugin?

2) in the “Cloudflare Workers” section do I need to add another cookies? for plugins like Peepso and Gamipress, as their cookie is only useful for logged in users. For this type of plugin the cookie bypass “wordpress_logged_in_” that’s enough?

3) I use “Media Cloud” plugin to offload images to AWS S3, configured with cdn subdomain in my cloudflare dns. This plugin also has option to load CSS and JS from S3 via CDN. Combined with your plugin, if I enable this option to serve CSS/JS via S3 on “Media Cloud”, is it possible to gain more performance? Or does it make no difference?

and I want to take this opportunity to congratulate you for the amazing support here on the forum. I saw several threads, and you answer everything. Congratulations ??

to satisfact Core Web Vitals warning “Serve static assets with an efficient cache policy” I selected “Browser Cache TTL = 1 year” on Cloudflare panel. This disrupts the plugin?

– Do not select a browser cache TTL in the CF dashboard it should always be set to Respect Header. If you want to add proper cache-control header for the static files enable the Add browser caching rules for static assets option in the plugin settings under the Cache tab of the plugin settings. Screenshot: https://i.imgur.com/k794Ylz.png

in the “Cloudflare Workers” section do I need to add another cookies? for plugins like Peepso and Gamipress, as their cookie is only useful for logged in users. For this type of plugin the cookie bypass “wordpress_logged_in_” that’s enough?

– If you want to bypass the cache for certain cookies you can enter that here: https://i.imgur.com/8FU8z11.png
There are already a list of default cookies that the plugin look for so in most cases you don’t need to add anything extra. The option has been given in special cases only.

I use “Media Cloud” plugin to offload images to AWS S3, configured with cdn subdomain in my cloudflare dns. This plugin also has option to load CSS and JS from S3 via CDN. Combined with your plugin, if I enable this option to serve CSS/JS via S3 on “Media Cloud”, is it possible to gain more performance? Or does it make no difference?

– Well, technically I don’t see any performance boost by that. Rather I see performance loss. Cloudflare CDN doesn’t ask you to change your hostname in any way to something like cdn.example.com. So, when a browser makes a request for example.com it can get all the data from the same place. But when you add more hostnames like cdn.example.com the browser has to make freash requests for those hostnames. This is why I personally host everything over Cloudflare. If you have extra money to spare, I will rather suggest you to take Cloudflare Pro + CF Argo which will give you unlimited image optimization, WAF etc. and Argo will give you smart routing and smart tiered cache which is amazing.

and I want to take this opportunity to congratulate you for the amazing support here on the forum. I saw several threads, and you answer everything. Congratulations

– Thank you so much for your love and support. ??