Browser-side caching relies on HTTP headers to know whether or not the content it has in its local cache is still valid. If it is, then it uses the local copy, rather than downloading the file from the server again. Many sites like whysoslow.com will report that you’re missing this HTTP header on your static files, which is normal, since you aren’t explicitly setting that in the files, since they’re mostly images and the like. In order to improve browser-side caching of your static content you could add mod_expires to your Apache configuration. This would add the necessary HTTP headers to make browser-side caching of your static content possible.<\/p>\n
Install mod_expires and add the following to the .htaccess:<\/p>\n
# Deflate output configuration
\n#
\nAddOutputFilterByType DEFLATE text\/html text\/plain text\/xml text\/javascript text\/css application\/javascript
\n#AddOutputFilterByType DEFLATE text\/html text\/plain text\/xml text\/css
\nBrowserMatch ^Mozilla\/4 gzip-only-text\/html
\nBrowserMatch ^Mozilla\/4\\.0[678] no-gzip
\nBrowserMatch \\bMSIE !no-gzip !gzip-only-text\/html<\/p>\n
ExpiresActive On
\nExpiresDefault “access plus 1 month”
\nExpiresByType image\/png “access plus 1 month”
\nExpiresByType image\/gif “access plus 1 month”
\nExpiresByType image\/jpeg “access plus 1 month”
\nExpiresByType text\/css “access plus 1 month”<\/p>\n
AddType image\/x-icon .ico
\nExpiresByType image\/x-icon “access plus 1 year”
\nExpiresByType image\/ico “access plus 1 years”<\/p>\n","protected":false},"excerpt":{"rendered":"
Browser-side caching relies on HTTP headers to know whether or not the content it has in its local cache is still valid. If it is, then it uses the local copy, rather than downloading the file from the server again. … Continue reading