Title: Leverage browser caching Last modified: August 30, 2016 --- # Leverage browser caching * Resolved [nerimizi](https://wordpress.org/support/users/nerimizi/) * (@nerimizi) * [10 years, 8 months ago](https://wordpress.org/support/topic/leverage-browser-caching-28/) * Hi all, with Google PageSpeed Insights the major issue is related to “Leverage browser caching” * There are the files: * Leverage browser caching Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network. Leverage browser caching for the following cacheable resources: [http://sumome.com/api/load/](http://sumome.com/api/load/)( expiration not specified) [http://load.sumome.com/](http://load.sumome.com/) ( 10 minutes) * Can you suggest me how to fix the issue ? * Thanks, nerimizi * [https://wordpress.org/plugins/sumome/](https://wordpress.org/plugins/sumome/) Viewing 1 replies (of 1 total) * Plugin Author [Sumo](https://wordpress.org/support/users/sumome/) * (@sumome) * [10 years, 8 months ago](https://wordpress.org/support/topic/leverage-browser-caching-28/#post-6535855) * [https://help.sumome.com/customer/en/portal/articles/1815157](https://help.sumome.com/customer/en/portal/articles/1815157) * SumoMe may appear to add time to your page load but whats happening is called asynchronous loading, meaning SumoMe yields to your site, loading as passively as possible, always giving precedence to your site. We do not block any content or scripts on your page from loading. Our back-end is powered by a world class cluster of web servers with an average response time of 8 milliseconds. * We’re always working on optimizing load times and file sizes. To optimize download speeds we use a global CDN (Content Delivery Network) to deliver all of our assets, and utilize keep-alive requests. While there are “multiple requests” being made, they’re using the /same/ connection without disconnecting, which has the same net effect as a single connection. * We utilize caching and build our CSS on a per-app basis instead of a singular CSS file for all apps because having you load only what you use is more efficient and optimal. Our CSS is combined per app (for the app and user-facing) because we never want to have your visitors loading the admin CSS. For admin’s in particular, there are a lot more assets that load compared to a normal visitor, because of all the additional Tools and UI for using SumoMe. * So with everything loading behind a CDN and with our use of caching, the majority of all your visitors will only load our files once. Rest assured, we’re fully aware and make conscious choices to deliver SumoMe asset’s in the most optimal way. Viewing 1 replies (of 1 total) The topic ‘Leverage browser caching’ is closed to new replies. * ![](https://ps.w.org/sumome/assets/icon-256x256.png?rev=3147974) * [Website Pop-up Builder by BDOW! (formerly Sumo): Pop-ups + forms for email opt-ins and lead generation](https://wordpress.org/plugins/sumome/) * [Frequently Asked Questions](https://wordpress.org/plugins/sumome/#faq) * [Support Threads](https://wordpress.org/support/plugin/sumome/) * [Active Topics](https://wordpress.org/support/plugin/sumome/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/sumome/unresolved/) * [Reviews](https://wordpress.org/support/plugin/sumome/reviews/) ## Tags * [browser caching](https://wordpress.org/support/topic-tag/browser-caching/) * 1 reply * 2 participants * Last reply from: [Sumo](https://wordpress.org/support/users/sumome/) * Last activity: [10 years, 8 months ago](https://wordpress.org/support/topic/leverage-browser-caching-28/#post-6535855) * Status: resolved