Plugin Contributor
iSaumya
(@isaumya)
Hi,
first of all, if your site has good/moderate traffic – you really don’t need to use the preloader. It is mainly for super low-traffic sites.
Also unfortunately there is no option to increase the delay between the requests. As the requests are handled asynchronously.
Thread Starter
Web Guys
(@webinfinitynz)
Thanks for the answer. 🙂
Some of the sites are quite low traffic, it’s just nice to have all the pages/post cached for when someone does land on a page.
I guess I could just preload the main / most popular pages & posts.
Or another idea. I also use Swift Performance, with page cache currently disabled so not to clash with yours. Could re-enable caching on Swift (as I can control the preload speed on that) then disable the fallback cache on your plugin?
Assuming they’re both compatible (so Swift handling the website level page cache and your plugin handling the CF cache), if Swift does its preload via curls, would that also preload the CF cache?
Thanks again!
Plugin Contributor
iSaumya
(@isaumya)
Some of the sites are quite low traffic, it’s just nice to have all the pages/post cached for when someone does land on a page.
I guess I could just preload the main / most popular pages & posts
– Well, it doesn’t work that way. If those pages don’t have much traffic – Cloudflare won’t keep them in cache – unless you get the Cloudflare Cache Reserve.
Also a lot of time when Cloudflare system sees requests are coming via cURL instead of an actual browser – it won’t cache the pages.
Could re-enable caching on Swift (as I can control the preload speed on that) then disable the fallback cache on your plugin?
– You can try but not sure if it will work. If that plugin modifying the cache-control header and not let this plugin take control over the cache-control header or if there are 2 cache-control headers, the Cloudflare cache might not work properly.
Thread Starter
Web Guys
(@webinfinitynz)
Many thanks for the info. That’s all clear.
