According to the web site optimization page, this blog is too big and loads too slowly:
Connection Rate Download Time 14.4K 70.21 seconds 28.8K 36.81 seconds 33.6K 32.03 seconds 56K 20.58 seconds ISDN 128K 8.66 seconds T1 1.44Mbps 3.86 seconds
For readers on a good cable/DSL connection, this shouldn’t be an issue; but the thought that it might take 20 seconds to load this page on dialup is sobering. I currently have the blog set to show six past days of content. I could set it to fewer in order to speed things up. Should I?
OK, the web site optimization page is sort of suspect, as it seems designed to get you to buy a book. Also, this week isn’t quite a typical one, as I have a 21K graphic element bulking up the total to 86K. But still, if it’s true…twenty seconds (or even sixteen) is forever….
Update: Based on suggestions in the comments, I cut a couple of days of posts off the tail, removed four small graphic images (although I like the “XML” boxes myself), and tried it again. Didn’t seem to make much difference:
Connection Rate Download Time 14.4K 61.58 seconds 28.8K 32.19 seconds 33.6K 27.99 seconds 56K 17.92 seconds ISDN 128K 7.43 seconds T1 1.44Mbps 3.20 seconds
*Note that these download times are based on the full connection
rate for ISDN and T1 connections. Modem connections (56Kbps or less)
are corrected by a packet loss factor of 0.7. All download times
include delays due to round-trip latency with an average of 0.2 seconds
per object. With 14 total objects for this page, that computes to a
total lag time due to latency of 2.8 seconds.
But I do think there’s something suspicious here. Not only does my host have gzip loaded, but if you do the back of the envelope arithmatic, some 70K of content should not take even two tens of seconds to download over a 56K connection. Even with some moderate packet loss.