Pre generate cache prior to visitor visiting site first

Currently there isn’t a supported way to do this. Generally, for server load, it is better to let it regenerate naturally.

Version 1.1.0 of Cache Enabler allows you to purge individual URLs very easily from top admin bar. I always recommend if you are making changes, etc. that you purge only the page that is needed, instead of purging entire cache across the entire site.

Caching of a page just needs a single request, which means frequently visited pages are cached immediately. As Brian said having the complete site cached at once can have a severe load impact on the server.

I know this has just been marked ‘resolved’, but I’d definitely second the OP’s wish/suggestion.

Just moved from Comet Cache Pro, to using Cache Enabler/CDN Enabler/KeyCDN (plus BWP Minify) and absolutely love it, but miss Comet Cache’s ‘Auto-Cache Engine’ function of reading an xml sitemap and filling the cache up.

Our WC site currently gives awful 1.5+sec ttfb scores on first request, but then a fabulous 35ms ttfb after the cache has been filled.

Manually browsing 400 pages ain’t much fun! ??

[Update: Discovered the ‘Warm Cache’ plugin and this seems perfect at filling Cache Enablers cache on a cron job and without too much stress to server]

The option to set a bot to crawl the website after the cache is completely emptied should be a must have. If the crawl can be set to scan only one post every 5 or 10 seconds it won’t impact the website performance at all even on a shared server.

If you have a first-time visitor just after you have emptied the whole cache, he will think that your site is just bad. He will leave with the impression that your site loads slow and won’t access it again next time.

In my opinion, this option should be taken into consideration for the main reason stated above. And I doubt it can’t be created in a way to not affect the performance.

Regards,