Speed up your site
- on 16/01/2012 (updated on 20/02/2014)
As we all know, Wolf is pretty fast with it’s page loading and general overall performance but you can always push it a bit more. If you do find your site to be slow (or starting to be) you can always try Funky cache or AS cache plugins to boost it a bit.
In most cases you don’t need any sort of caching but you can still speed it up a bit with small addition to your .htaccess file. For the past few weeks I have been poking around with Page Speed and Woorank, just for fun and curiosity.
Here are “before” and “after” images of the pageload made via Woorank:
As you can see, there is a slight difference in speed and I must admit that the whole site runs smoothly and quicker (not that it hasn’t before either).
Just gzip it!
When I first ran Page Speed it gave me few advices among other things (like optimize images etc.) and one of them was Enable Compression. So I surfed a bit and found this code:
The above snippet will gzip all your
Enable browser cache
This is useful when you have design rich website with lots of graphic elements.
# BEGIN Cache-Control Headers <ifModule mod_headers.c> <filesMatch "\.(ico|jpe?g|png|gif|swf)$"> Header set Cache-Control "public" </filesMatch> <filesMatch "\.(css)$"> Header set Cache-Control "public" </filesMatch> <filesMatch "\.(js)$"> Header set Cache-Control "private" </filesMatch> <filesMatch "\.(x?html?|php)$"> Header set Cache-Control "private, must-revalidate" </filesMatch> </ifModule> # END Cache-Control Headers
This one should be “common sense” in general, but there are always exceptions, especially with new wannabe developers/designers.
Most image editors have “Save for Web & Devices” button somewhere, so use it!
.png – where you need transparency, always export it at 72dpi and quality between 60-80 should suffice
.jpg/.jpeg – for everything else (dpi and quality like above)
Last but not least, you could compress your
.js with just a few clicks. Here are few Compressors which you can use to accomplish that.
That should be it. If you have any suggestions, please use comments section.
Stay tuned, next article is about moving whole site from localhost to live server.blog comments powered by Disqus