Support » Plugins » [Plugin: WP Super Cache] Leverage Browser Caching using the W3TC htaccess script

  • I installed the W3 Total Cache plugin but to fair, it was a bit much for a small blog so I resorted back to the trusted WP Super Cache. Fortunately my knowledge has improved albeit marginally but I thought of this to help speed up my site.

    I check Google Page Speed every now and then and the last time I did I noticed that a few scripts were not being “measured” by the leverage browser caching bit. (Hope your loving my terminology)

    I had a look online for a trick or at least a substantial method to improve on this and I came across various scripts for the .htaccess file pretty much all saying the same thing about expiration which was the issue I had. But then, I spotted an old .htaccess file in my directory when doing these checks so I had a look at it appears to be a much longer and far more in depth piece of script that would pick up those files that are not already being picked up by GPS.

    So I took the script that was from the W3TC plugin which was left behind, stuck it into my new one and now I’m waiting for Google to crawl away and notice the coding to improve my Page Speed.

    Ethically, I feel bad for doing this but 1. Is it deemed acceptable? 2. Will it work? and 3. Should I be happy to have figured a little smart answer out?

    The piece online that many recommend is this:

    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType image/jpg "access 1 year"
    ExpiresByType image/jpeg "access 1 year"
    ExpiresByType image/gif "access 1 year"
    ExpiresByType image/png "access 1 year"
    ExpiresByType text/css "access 1 month"
    ExpiresByType application/pdf "access 1 month"
    ExpiresByType text/x-javascript "access 1 month"
    ExpiresByType application/x-shockwave-flash "access 1 month"
    ExpiresByType image/x-icon "access 1 year"
    ExpiresDefault "access 2 days"

    However, I’m wondering if this is better:

Viewing 4 replies - 1 through 4 (of 4 total)
  • Upon looking back, I’m wondering whether having the code wrapped in these ‘##’ on the bigger script makes a difference or not. And also, whether it is a problem having this when using the WPSC plugin as it states for the htaccess file to have a certain script in particular.

    I just don’t know really?!

    For apache the # only comments the line it appears on.

    Anyway, what was “too much” about W3TC?

    Hi. Mr. Townes. Your W3TC gets so many rave reviews. Thanks. I was wondering if you are planning to have an update to the latest version of wordpress 3.3.2?

    I don’t know how to leverage browser caching either. I’m not sure if one of the boxes to “tick” does that function or not.

    When I went to check speed tests for, I was still getting that error message.

    I’ve tried to cut and paste the code to the .hta access file two different times but to no avail, so I was thinking it may be included somewhere in the plugin, but not sure.

    A release will be out this month.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: WP Super Cache] Leverage Browser Caching using the W3TC htaccess script’ is closed to new replies.