Here’s how caching works
Basic caching uses PHP to serve up pages that are stored on disk. So PHP, WordPress and Wordfence execute and interrupt execution to serve up a pre-rendered page early in the execution cycle. This provides a nice speed increase without having to edit your .htaccess. Some sites can’t do this which is why we included the feature. If you aren’t seeing a performance gain, my guess is that your site does some heavy lifting early on in the execution cycle and this bottleneck isn’t solved by basic caching.
Falcon Engine modifies your .htaccess to have your web server serve pre-rendered pages directly to the user. We use a different directory structure which reduces stat() activity on your server disk and is therefore faster and gets better performance than other caching plugins. Please see https://www.wordfence.com/blog/ for more info on this
So, basic caching doesn’t rely so much on the user click to get the page I think.
Currently, there is not a way to have both, specifically because live traffic increases some load on the server. Your site is still being monitored and alerts are still working. Its the calls to the database to serve up information on the screen that use up the resources.
tim