RaGhul, on 13 April 2010 - 04:53 PM, said:
There's a WordPress plugin called 'W3 Cache' that caches your page. It's supposed to make it faster. I tried it for a day, but it messed up my WordPress theme, lol.
Considering the benefits of serving a static page versus dynamic content, it would be well worth figuring that out.
RaGhul, on 13 April 2010 - 04:53 PM, said:
As Coffee said, it's a
compression algorithm for compressing content from the webserver to the client browser. Given you're serving about 34K of data, gzip compression should yield about a 75% (in some cases more) reduction in size transmitted from the server to the client. Couple your server with no compression and the fact that you've also told the client not to cache ANYTHING from the webserver, you're unnecessarily spending time re-serving UNcompressed data to a client EVERY time they visit the site - from the headers visiting your site this evening:
HTTP/1.1 200 OK
Date: Wed, 14 Apr 2010 05:50:30 GMT
Server: Apache
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Pragma: no-cache
X-Pingback: http://skeetabyte.com/xmlrpc.php
Set-Cookie: PHPSESSID=p1j9plhvn47a6m8u5b5e57jif1; path=/
Set-Cookie: wassup=MTdmMGQxYzJiMTY2NDM2ZTI3YTM1Yzg0YWFkZDgwMzE6OjEyNzEyMjY5MzE6Ojo6MjA5LjY4LjEuNjM6OnJ1aXMucGFpci5jb20%253D; expires=Wed, 14-Apr-2010 06:40:31 GMT; path=/
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8
RaGhul, on 13 April 2010 - 04:53 PM, said:
And... is there really that much javascript? I haven't sniffed around all the WP files yet, so I honestly don't know.
125K isn't a LOT of javascript, but given the site's design most browsers won't start displaying the page until the javascript has been downloaded and compiled as it's all in the page HEAD. Someone on a slower connection will very likely see page load delays, as would someone visiting the site while the server running it is under load. Compression and caching - if you aren't changing the content too much (and things like images and javascript aren't changing), it would be best to allow caching at least for a day or so, along with implementing compression. There are at least 1371 sites hosted on that server alone that matched a reverse-IP lookup to the server hosting your site, so the fewer resources your site requires to actually serve content, the better.
Consider using
http://ismyblogworking.com and/or
http://redbot.org to get more info about your blog, and hints as to what else you can do to make it more efficient.