JQuery, Prototype, and MooTools Benchmark – SlickSpeed


Before I even start, let me state that I’m a JQuery fan. Ever since I’ve started with JavaScript frameworks I’ve weighed the pros and cons, and trust me there are a lot. You’ll always find people arguing Prototype, JQuery or MooTools. I went with JQuery because it could do all that I wanted with the least amount of bloat. I’m sorry, Prototype may do a hell of a lot, but I don’t think that I could make enough use or that 100 KB to justify it. Plus, Prototype can’t even handle basics on its own without having to piggy back off of script.aculo.us and it’s effects library.


Now with every new version of a Framework that comes out, this argument comes up again and again. Finally, we have something to put the arguments to rest.


In my personal testing, I’ve found that JQuery 1.21 leads the pack, but only in Internet Explorer. In Firefox it comes in dead last. Does this discourage me? Maybe a lil’ bit. Am I going to stop using JQuery and switch to Prototype? I think not.

What Do You Need?

It all depends on your uses for said framework. From the looks of it, Mootools looks more like a full fledged programming language. With all the definitions of new objects, etc. If, for some reason I’m needing to build an application in JavaScript then I’ll revisit it. But until now, the most JavaScript that I’ll be doing is so simple effects on elements (shows, hides, slides, class changes, etc) and a couple Ajax requests.

For this I don’t think I should suffer the 120 KB that Prototype has to offer, even though it’s blazing fast in Firefox. With that said, even if I hate Internet Explorer, it is still, by far, the most popular browser out there. So I take comfort in the fact that the majority of my audience is getting the speed benefits of JQuery.


  1. Well, why would I choose between say, Last.fm and Deezer.com? They basically do the same thing – they both play music – but not exactly in the same way (one is running smart radios, and the other plays on demand…)

    Depending on my needs, I pick the one or the other : they also share the fact they’re free and easy to use!

    If you know Javascript, you can learn those libraries in no time, but with little energy I admit. You can even use them on the same web pages, cause they’re not in conflict, they are all just awesome, and getting awesomer by the time I’m writing this.

    PS : awesome blog 😉

    Ben’s last blog post..“Nous avons été visités” affirme un astronaute célèbre

  2. tried the test and seems that Prototype is a much faster framework. I’m currently using both jquery and mootools but it seems Prototype has it’s good point’s I might give it a try also.

    Anyways… great article…

    • Make sure you test under all browsers, as certain functions are faster on different browsers. Just did a test on Safari 4 (OS X) and Prototype is, by far, the slowest.
      Dojo was blazing, with Mootools and jQuery coming in a close second.

  3. Juan García says:

    Do you guys know when they will update slickspeed libraries to the latest versions?
    At least updating to jQuery-1.3.2 will show clearly the winner.

  4. I would like to build a javascript in default.ctp
    What is the process?

  5. I tried Prototype, JQuery, and mootool . So my winner is mootool. Simple, easy, and fast to learn. My new project (http://quickmessageapp.com) base on mootool 🙂

  6. Abdul Awaes says:

    Nice Post!