0.5-0.8 seconds is significant for me, becose some of my users have too much hops (asia) to my servers and usually pages is loading in 1.5 seconds. 0.8 – is the half (!), not filled with any useful actions page load time, too big comparing with total page load time.
Yes, mootools is loading from page header.
According to YSlow or Page Speed recommendations I could move mootools to the end of the page, but I’m worry about document.write calls, that could not modify page objects in some initialization functions that you’re using and I donw’t deeply know…

So my questions is:
1) Can I do “late” or “parallel with loading static multimedia objects” initialization of mootools library somehow?
2) can I safety move whole mootools (or some parts of the library) to the page bottom to prevent browser blocking on objects loading?
3) what methods you’ll advise to speedup parallel page loading with whole (core and nc) mootools?

Does the method “setStyles” cause multiple reflows?

[code]
element.setStyles({
height: "100px",
display: "block",
fontsize: "130%"
})
[/code]

will that cause 1 or 3 reflows?

I will also have to re-write some of my code.

I’m wandering if Mootools should remove .each(); to encourage good performance practice? Or at least put a note in the documentation warning that it will slow down the code…

Also, is DocumentFragment use in Mootools to speed accessing the DOM?