If you have got ever run your WordPress website through “Google Page Speed Insights” or Pingdom then you have got in all probability seen that massive yellow Leverage Browser Caching warning. which is perhaps why you complete up at this post. nowadays we are going to dive into what this warning suggests, however, it affects you, and the area of your choice unit because it pertains to your WordPress website.

What is Leverage Browser Caching Warning?

The leverage browser caching warning is touching on your browser cache. Whenever you visit an internet site, it downloads assets, like HTTP pages, CSS, JavaScript, and other pictures into your browser’s native or local cache. This manner doesn’t need to retrieve them on each page load. The warning itself is coming back once your web or hosting server, or a third-party server, doesn’t have the proper HTTP protocol cache headers enforced. Or the headers may exist, however, the cache time is ready too short.

Fix the Leverage Browser Caching Warning in WordPress

When it involves fixing the leverage browser caching warning there area unit one or two completely different situations that area unit sometimes encountered by WordPress users. the foremost common one is that your internet server isn’t properly designed. The second irony is that Google Analytics ’ script offers the United States the warning. and therefore the third is alternative third-party scripts returning the warning. See what your choices area unit below.

1. Leverage Browser Caching on Server

The first and most typical reason the leverage browser caching warning is triggered is that your internet server doesn’t have the suitable headers in situ. within the screenshot below in Google Page Speed Insights you may see the rationale is as a result of AN expiration isn’t such as. once it involves caching their area unit 2 primary strategies that area unit used, Cache-Control headers and Expires headers. whereas the Cache-Control header activates client-side caching and sets the max-age of a resource, the Expires header is employed to specify a selected purpose in time the resource is not any longer valid.

2. Leverage Browser Caching and Google Analytics

The second most typical leverage browser caching warning comes from Google Analytics. this is often reasonably ironic seeing as this is often Google’s script. the problem is that they set an occasional pair of hour cache time on their quality, as seen within the screenshot below. They possibly do that as a result of it for a few reasons they were to change one thing on their finish they need all users to urge the changes as quickly as doable. but there’s the simplest way to urge around this, which is by hosting Google Analytics script on your server. Please remember although that this is often not supported by Google.

3. What regarding alternative third Party Scripts?

If you’re running a business on your WordPress website, presumably you have got extra third-party scripts running to trace conversions, A/B tests, etc. This would possibly embody scripts like Facebook conversion pixels, Twitter, CrazyEgg, Hotjar, etc. sadly since you can’t host those regionally there’s nothing abundant that will be done as you don’t have management over the caching of these third-party assets. except for several smaller sites and bloggers, you presumably will get eliminate that leverage browser caching warning by following the recommendations on top of it.

Thanks for sharing. Sharing is caring.

Fix the Leverage Browser Caching Warning

The article was published on October 29, 2017 @ 10:05 AM

Leave a Comment


  • You have made some really good points there. I checked on the web for more information again and found most individuals will go along with your views on this website.|

  • Never given much thought about this issue.
    Very informative and helpful article. Infact this article compelled me to check my page speed using Google page speed insights.
    Thankyou Salim