Many thanks for your feedback!
That’s right, your understanding is correct I think.
WP Fastest Cache explains here their preload that way:
“A cached file is typically generated after a user initially visits a page. This creates a delay for the very first user who views it.
The preload allows you to create the cache of all the post, page, category, homepage etc. periodically, which helps much in improving future page loads.”
And Flying Pages does exactly what you described.
Now, I forgot to mention the reason why that set that way there:
It’s a low traffic site and WPFC suggests using their preload for that sort of sites, for the reasons that are described above.
The preload had nonces issues with online forms that were resolved by adding their cron that deletes preload files every 10 hours.
I don’t really know what “LSWS” and “OpenLiteSpeed Web Server” stands for but this site is on a shared server with a “LiteSpeed Web Cache Manager” menu on cPanel and the Crawler is not enabled there.
So, my question finally would be:
Is there any special configuration to take care of especially for:
– low traffic sites
– online forms (maybe simply exclude them somewhere?)
and would ESI really be helpful for such cases?
Thanks again!