How to Fix the Leverage Browser Caching Warning in Blogger? with Video Tutorial

At some point in time when you are running speed tests with your
website you will most likely encounter the all popular “leverage browser
caching” warning in Google PageSpeed Insights. And we are referring to
the one originating from Google’s analytics.js script. In this post today we are going to show you a couple options on how to easily setup local analytics to fix this warning. Depending upon your environment you might also see
a slight performance improvement. We have also included a new way to
more easily do this for those of you running Blogspot.

How to Fix GA Leverage Browser Caching Warning

Normally the way we would fix a leverage browser caching warning would be to simply add expires headers.
However, since this is a 3rd party script hosted on Google’s servers we
have no control over the headers. There are two different options below
you can use to fix this warning.

So! how to fixed It? 

This rule triggers when Page Speed Insights
detects that the response from your server does not include caching
headers or if the resources are specified to be cached for only a short

Follow this step .

1. Go to Blogger Dashboard

2. Click on Themes
3. Click on Edit HTML
4. find Clrt+F ” <b:skin><![CDATA[ ” Paste Cache Coding Above this Yellow Code.

 <include expiration=’7d’ path=’*.css’/>
<include expiration=’7d’ path=’*.js’/>
<include expiration=’3d’ path=’*.gif’/>
<include expiration=’3d’ path=’*.jpeg’/>
<include expiration=’3d’ path=’*.jpg’/>
<include expiration=’3d’ path=’*.png’/>
<meta content=’tue, 02 jun 2020 00:00:00 GMT’ http-equiv=’expires’/>

Watch Video


As you can see there are some great alternatives out there for page speed if you are trying to fix the Google Analytics leverage browser caching warning
in PageSpeed Insights. You might even see a small performance
improvement after some days. Have you experimented with  this method? If so we would love to hear your thoughts below. thankyou


  1. CreebHills July 16, 2017
  2. kamaldhital July 17, 2017
  3. kamaldhital July 28, 2017

Leave a Reply