The Speed Boost Cache code is htaccess Browser caching code. You may see significant website load speed performance or you may only see minor website load speed improvement, but you should see some website performance improvement. You can do benchmark/website load speed/performance testing/checking with Firefox, Firebug, Firephp and Yslow or you can use one of the online website speed testing sites such as Google PageSpeed Insights, Pingdom or GTmetrix.
Internet Speed Testing site: InternetAdvisor
Important Note: If you are already have a caching plugin installed (WPSC, W3TC, WPFC, Comet Cache, WP Rocket, etc) and have already added your caching plugin’s Browser caching code in BPS Custom Code then do not also add the BPS Speed Boost Browser caching code. Adding duplicate or redundant Browser caching code will not improve website performance and may actually cause your website to perform/load slower. See this forum topic for additional detailed help information: https://forum.ait-pro.com/forums/topic/bps-speed-boost-cache-custom-code-notice/
1. Copy the Speed Boost .htaccess code below into this BPS Root Custom Code text box: CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
2. Click the Save Root Custom Code button.
3. BPS Pro 11.9+ & BPS .53.8+: Go to the BPS Security Modes page and click the Root Folder BulletProof Mode Activate button.
3. Older BPS versions: Go to the BPS Security Modes page, click the Create secure.htaccess File AutoMagic button, select the Activate Root Folder BulletProof Mode Radio button and click the Activate|Deactivate button.
Notes: If you are using php/php.ini handler htaccess code (or add php/php.ini handler htaccess code to BPS Custom Code at a later time) then the correct order of htaccess code in the CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE text box is: php/php.ini handler htaccess code first and then Speed Boost .htaccess code goes after/below your php/php.ini handler htaccess code in the CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE text box.
# BEGIN WEBSITE SPEED BOOST # Time cheat sheet in seconds # A86400 = 1 day # A172800 = 2 days # A2419200 = 1 month # A4838400 = 2 months # A29030400 = 1 year # Test which ETag setting works best on your Host/Server/Website # with Firefox Firebug, Firephp and Yslow benchmark tests. # Create the ETag (entity tag) response header field # This is probably not the optimum choice to use. #FileETag MTime Size # Remove the ETag (entity tag) response header field # This is most likely the optimum choice to use. Header unset ETag FileETag none <IfModule mod_expires.c> ExpiresActive on # ExpiresByType overrides the ExpiresDefault... # cache expiration time of 2 days|A172800. ExpiresDefault A172800 ExpiresByType image/jpg A4838400 ExpiresByType image/jpeg A4838400 ExpiresByType image/gif A4838400 ExpiresByType image/png A4838400 ExpiresByType image/bmp A4838400 ExpiresByType image/x-icon A4838400 ExpiresByType image/svg+xml A4838400 ExpiresByType text/javascript A4838400 ExpiresByType text/x-javascript A4838400 ExpiresByType text/css A4838400 ExpiresByType text/html A4838400 ExpiresByType application/x-font-ttf A4838400 ExpiresByType application/x-font-woff A4838400 ExpiresByType font/opentype A4838400 ExpiresByType application/x-shockwave-flash A4838400 ExpiresByType application/x-javascript A4838400 ExpiresByType application/javascript A4838400 ExpiresByType video/mp4 A4838400 ExpiresByType video/ogg A4838400 ExpiresByType video/webm A4838400 </IfModule> <IfModule mod_headers.c> <FilesMatch "\.(js|css|flv|ico|pdf|avi|mov|ppt|doc|mp3|wmv|wav|gif|jpg|jpeg|png|swf|webm)$"> Header append Cache-Control "public" </FilesMatch> <FilesMatch "\.(txt|html)$"> Header append Cache-Control "proxy-revalidate" </FilesMatch> <FilesMatch "\.(php|cgi|pl|htm|xml)$"> Header set Cache-Control "private, no-cache, no-store, proxy-revalidate, no-transform" Header set Pragma "no-cache" </FilesMatch> </IfModule> <IfModule mod_deflate.c> AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css text/javascript AddOutputFilterByType DEFLATE application/javascript application/x-javascript AddOutputFilterByType DEFLATE application/x-httpd-php application/x-httpd-fastphp AddOutputFilterByType DEFLATE application/xml application/xhtml+xml application/xml-dtd AddOutputFilterByType DEFLATE application/rdf+xml application/rss+xml application/atom+xml AddOutputFilterByType DEFLATE font/otf font/opentype application/font-otf application/x-font-otf AddOutputFilterByType DEFLATE font/ttf font/truetype application/font-ttf application/x-font-ttf AddOutputFilterByType DEFLATE image/svg+xml # Drop problematic browsers BrowserMatch ^Mozilla/4 gzip-only-text/html BrowserMatch ^Mozilla/4\.0[678] no-gzip BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html # Make sure proxies don't deliver the wrong content Header append Vary User-Agent env=!dont-vary </IfModule> # END WEBSITE SPEED BOOST
Extra General Info:
You can use the code exactly as is or if you want to see if you can get a couple more milliseconds of speed:
Test using no ETags by commenting out (adding a pound sign #) all the ETag lines of .htaccess code below (#FileETag MTime Size, #Header unset ETag, #FileETag none) and benchmark test website performance, then benchmark test using Header unset and FileETag none (this is currently the default code shown below) and then benchmark test using FileETag MTime Size (uncomment FileETag MTime Size and comment out #Header unset ETag, #FileETag none). Whichever ETag combination/choice makes your website perform the fastest is the one you want to use/keep. On Go Daddy it seems that using Header unset ETag and FileETag none is slightly faster in milliseconds (as shown below).
Testing examples explained above are here: http://forum.ait-pro.com/forums/topic/htaccess-caching-code-speed-boost-cache-code/#post-9707