Title: Mobile Cache Preload Last modified: September 30, 2022 --- # Mobile Cache Preload * Resolved [digitalkult](https://wordpress.org/support/users/digitalkult/) * (@digitalkult) * [3 years, 8 months ago](https://wordpress.org/support/topic/mobile-cache-preload/) * Hey Team, * we are using user agent groups to avoid breaking the Mobile rendered menu when creating the page cache. * The cache preload only seems to work for the desktop version. * Is there a way to prime the tablet and mobile cache? The mobile versions don’t seem to get preloaded :/ * Thank you in advance 🙂 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmobile-cache-preload%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 7 replies - 1 through 7 (of 7 total) * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [3 years, 8 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16064414) * Hello [@digitalkult](https://wordpress.org/support/users/digitalkult/) * Thank you for reaching out. The Cache Preload needs the sitemap URL to work. If you are using User Agent groups and preloading the pages, this means that the cached (preloaded page) will also be created for mobile/tablets as well as for desktop users. If you are searching for a separate folder, you will not find one because the cached pages are in the same folder. I’ve checked your website using a tablet and a mobile phone and it’s as fast as browsing through the desktop version. Can you please share what made you think that the pages are not preloaded for mobile users so we can possibly enhance this for other users? Thanks! * Thread Starter [digitalkult](https://wordpress.org/support/users/digitalkult/) * (@digitalkult) * [3 years, 7 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16067825) * Hey Marko, * i usually use redis and monitoring on putty what pages get created. I guessed its a redis bug so i used page enhanced to replicate it. * _index_slash_ssl.html looks like the desktop page _index_slash_phones_ssl.html phone page _index_slash_tablets_ssl.html tablet * i waited for the warming up to finish finish some times. the phones_ssl only gets created when someone opens the page on browser. The warmup does not create these by itself. * The first page it is DOM 1,5 seconds, the second 500ms. Maybe the performance was good on your try because someone already visited the page. * Desktop is fine. When you enter the page mobile its cold. * Do you have any idea why these pages dont get created on warmup? I can send you ftp credentials if you have any idea. If there is some tweeking needed i can also ask my customer to get you payed. * Its really important to get good performance on mobile 🙂 * best regards and thank you in advance * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [3 years, 7 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16068746) * Hello [@digitalkult](https://wordpress.org/support/users/digitalkult/) * Thank you for your feedback. I am testing this now and thank you for the information provided. Let me check this more and I’ll get back to you sith more info. Thanks! * Thread Starter [digitalkult](https://wordpress.org/support/users/digitalkult/) * (@digitalkult) * [3 years, 7 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16068968) * Thank you for the quick reply. If you have any details just let me know. As mentioned, if it needs a custom solution we are also willing to pay for a working mobile preload 😀 best regards * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [3 years, 7 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16072456) * Hello [@digitalkult](https://wordpress.org/support/users/digitalkult/) * Thank you for your patience. I can confirm that the Cache Preload does not create files for mobile and tablets. I’ve spoken with the team and opened a [GitHub ticket on your](https://github.com/W3EDGE/w3-total-cache/issues/567) behalf in our repository, so please make sure to check the progress of the ticket regularly. This requires some work so it’s not a quick solution. I’ll see if I can provide more details for any custom fixes. * Thanks! * Thread Starter [digitalkult](https://wordpress.org/support/users/digitalkult/) * (@digitalkult) * [3 years, 7 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16074388) * Hey Marko, * thank you for your feedback. I would love to use W3TC for this project 🙂 * I searched for alternatives, sadly WP-Rocket does the job just perfect without further configuration. * If the mobile preload is solved i will give it another try. * best regards from germany * Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * (@vmarko) * [3 years, 7 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16074876) * Hello [@digitalkult](https://wordpress.org/support/users/digitalkult/) * Thank you for your feedback. We are working on this feature and it will be added to future releases. Thank you for your patience. Viewing 7 replies - 1 through 7 (of 7 total) The topic ‘Mobile Cache Preload’ 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/) * 8 replies * 2 participants * Last reply from: [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/) * Last activity: [3 years, 7 months ago](https://wordpress.org/support/topic/mobile-cache-preload/#post-16074876) * Status: resolved