Last week I had some spare time and took a look at the Ajax hype. Instantly my attention was drawn by the loaders and to say the least, the load time on the WordPress blogs. Since I wanted to implement Ajax at my site, it was a bit of a turn off.

I first looked of course at the Gianni Milanesi’s AjaxWP. This looks promising if you like some DHTML in combination with Ajax. It’s also easy to setup… so what’s the problem? Well, it’s using Prototype, Scriptaculous and a history library. Which are all fine JavaScript libraries but do not improve load time. In fact, according to www.websiteoptimization.com it takes about one minute on a 33k6 telephone line on its first visit to completely load the site (without browser rendering). The Bloxpress 2 is a very fine WordPress theme, with a high coolaid level. But again, the load time is nothing to be proud of. And it’s a theme, I wanted my own the Brajeshwar theme to have Ajax.

I personally don’t like libraries, because you either use you nasty hacks because they don’t do what you want, or they just are far to big, which then you have a problem with legacy clients (which the processor can’t cope) or dialup users, which are very grateful that they could actually use your site within a minute

Because I want to use Ajax to improve the download and render time of the site instead of making it worse by implementing those libraries, I decided to write my own implementation.

Last Modified : August 12th, 2006 Filed under : JavaScript TAG(s) : AJAX, cached, JavaScript, latency, page-loading, WordPress Navigate : Previous post / Next post