I liked the point that was made in this books foreword: if you don't think site speed matters, put in some code that artificially delays loading your pages for ten seconds - and report back in a week..
Well, yes and no. Yes, it is all about trimming the fat, but how and what you trim are worth detailed discussion. And yet..
I'm not happy about that. Realistically I realize that the overwhelming majority of visitors here have at least DSL speed and most probably have much better. Yet I still hate to think of some poor person stuck on a 56K modem trying to pull down this page - it could easily be 30 seconds before it's all done. Of course a good chunk of text should appear quickly, and I can at least hope that would keep them happy.. maybe.
The book does talk about mod_perl, which I should use (and have just been lazy about) and gzip encoding, which I never even thought about until reading this. but that's hardly the only advice I found interesting here.. and yet, again, that push from reality: for most readers nowadays, a few hundred thousand bytes doesn't matter. For regular readers, it matters even less, because a lot of it will be cached..
So, overall, what do I think? Probably still worth reading, but I'm not going to get slimmed down to the 34K page size that the author considers "ideal". I am going to think about breaking some of the very largest pages into sections, but people don't like that either (I don't like it myself).
What's your thought? Is the web too bloated? Are you still stuck on dialup and cursing pages like this? What's to be done about it?
Tony Lawrence 2007-12-20 Rating:
Order (or just read more about) Speed Up Your Site from Amazon.com
Got something to add? Send me email.
More Articles by Anthony Lawrence © 2011-04-28 Anthony Lawrence