Title: W3TC don’t follow preload timing settings Last modified: May 24, 2019 --- # W3TC don’t follow preload timing settings * Resolved [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/) * As I would like to keep my objects, thus pages in cache for a longer period, I tried setting the following values to 21600 seconds. – Default lifetime of cache object – Garbage collection interval – Max lifetime object Then I saved the settings -> Nothing changed I saved the settings -> Nothing changed either. It keeps warming up some (not all) of the submitted pages every hour. * Is there another setting I should consider ? Viewing 13 replies - 1 through 13 (of 13 total) * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11567819) * Hello, * Are you referring to Cached pages or objects? Are both DB cache and Object cache enabled? * Thread Starter [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11567977) * DB Cache and object cache are both enabled (memcached). As I understand it, objects influence page caching/speed delivery. The settings I’m talking about are: **Page cache :** Maximum lifetime of cache objects (Garbaged is only for disk caching) **Object cache :** Default lifetime of cache objects, and Garbage collection interval * My Database cache current settings : Maximum lifetime of cache objects:3600 Garbage collection interval: 7200 * Should I also set these 2 last settings to that same 21600 value? Any drawback to consider? * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11568571) * Hello, How long a page is cached, depends on the value of Browser Cache => HTML& XML => Expires header lifetime * Thread Starter [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11574200) * Changed that settings too, and indeed, the preloaded pages now have a 6 hours lifetime, and will renew much less often, as expected. * However… I still find many of my pages not preloaded: when I take a look at the response of some sitemap declared pages, the headers state the page was last- modified at the exact same moment I opened it, whenever it should have been created somewhere in the last 6 hours, if properly warmed up. * The settings allow way enough time to warm up every page, so why so many pages won’t get warmed up as supposed to? * Thread Starter [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11579026) * Do you need more informations to troubleshoot this issue? * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11579430) * Hello, * Are you using a server cronjob (using crontab) to run WordPress scheduled events? If not, the preloader will only be triggered at the end of every request, which is not that often in your case. * Thread Starter [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11579831) * Hi Marko, Yes, we do use a cronjob, so that the preloader get triggered every 2 minutes. * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11580471) * Hello, * Does your sitemap contain all the pages? - This reply was modified 6 years, 10 months ago by [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/). * Thread Starter [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11580564) * Not all, but most of the pages are in the sitemaps. And on a regular basis, some of pages that are in the sitemaps but won’t get preloaded. * Thread Starter [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11583001) * I also checked for these pages that they were set as indexable through Yoast SEO. * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11583260) * Hello [@schwipps](https://wordpress.org/support/users/schwipps/), * You should add logging. Logging is available in wp-cli now. * So, instead of calling wp cron via crontab – you should call it directly via wp w3-total-cache pgcache_prime * And track the output which pages/sitemap positions are primed by script. * Thread Starter [T4ng](https://wordpress.org/support/users/schwipps/) * (@schwipps) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11591732) * I can already see, from the server logs, which page have been crawled by the preload or not. Would this method will give us more details about what goes wrong? * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11593086) * Hello, * Yes, as suggested in the previous post. Viewing 13 replies - 1 through 13 (of 13 total) The topic ‘W3TC don’t follow preload timing settings’ is closed to new replies. * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806) * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/) * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq) * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/) * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/) * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/) ## Tags * [cache](https://wordpress.org/support/topic-tag/cache/) * [preload](https://wordpress.org/support/topic-tag/preload/) * [settings](https://wordpress.org/support/topic-tag/settings/) * 13 replies * 2 participants * Last reply from: [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * Last activity: [6 years, 10 months ago](https://wordpress.org/support/topic/w3tc-dont-follow-preload-timing-settings/#post-11593086) * Status: resolved