Hello mrlb,
Thank you for reaching out!
By default, NitroPack will not optimize any pages with active login sessions or carts, in order to avoid serving cached content which might not be relevant to the current user experience.
Also, with the Exclude URLs setting, you can specify a list of pages you would not like to be optimized.
The free plan of Cloudflare is indeed limited to only 3 page rules. Unless you want to upgrade your plan, the page rules should be chosen wisely.
If you need any further assistance, please feel free to open a ticket with our support team: https://support.nitropack.io/hc/en-us/requests/new
Best regards!
Thread Starter
mrlb
(@mrlb)
Thanks for your reply @silvenatodorova
NitroPack is working great there is no doubt about that.
The issue is getting cloudflare to cache and bypass appropriately – and with the limitation of three rules it is simply not possible to achieve a desirable result.
To anyone else following this I found a work around that works consistently well with WordPress/Woocommerce + Cloudflare + NitroPack.
Here’s what you do:
No changes to NitroPack required.
Setup a cloudflare work to bypass when it detects a wordpress/woocommerce cookie. Not need to add any page rule that I can see.
And presto both CF and NP will give you HIT when there are no WP/WC cookies active for the page.
Now, the interesting finding is that I would actually get slightly better pagespeed scores when you don’t use the Cloudflare worker caching. The difference of a few points. I don’t entirely understand why but I suspect there might be a little added latency to rule to CF worker. So I have decided to turn CF caching off. But I suspect if you a decent amount of traffic then maybe having CF caching on might help. I would have to do a load test to be sure.
-
This reply was modified 4 years, 3 months ago by
mrlb.