Replies: 0
Hi!
Is there any way to see which pages have been primed? We are trialing W3TC on a secondary shop of ours but so far it seems that priming has no effect. We are using another caching plugin on our main shop and the second everything is primed, the shop is laser fast, but with W3TC, even though I can see the cron event (w3_pgcache_prime) running every 900 seconds, it seems that most pages are being delivered without caching.
So what basically happens, if I go to the page (using a different browser, not logged in), it takes the server some time for the Woo single product pages to load (we use lots of plugins due to many customisation options, hence the need for caching). Once the page has been loaded, reloading the page and going back and forth between the page and another page is as fast as expected, but if I now use yet another browser to access the same product page again, it takes the “non-cached” amount of time to load once again. So it seems that for whatever reason, everyone accessing a page for the first time gets to see an uncached version despite having Opcode, Browser, Page, Database and Object Cache enabled and we have REDIS installed on the server, so e.g. the database cache runs with REDIS.
Bottom-line, while I must say there are tons of options, hence the reason why we trial the plugin as we are missing some options with our current cache plugin, the result so far isn’t satisfying and I am sure there must be a reason why accessing the page doesn’t hit the cache. So is there any statistics (free version) or log to get an idea what is going wrong?
Regards
Alex
