4 ms·
Care to provide numbers how "big" that DOM rendering overhead is? Saving HTTP request is very important ant very noticeable, especially on mobile (high latency
by rimantas 15y ago
Care to provide numbers how "big" that DOM rendering overhead is?
Saving HTTP request is very important ant very noticeable, especially on mobile (high latency).
DOM overhead with sprites is negligible in comparison.
- franze 15y agoyeah, i agree totally, but even better are no icons at all. i don't have exact figures by hand, but one sites (which used sprits very very heavily) we managed to save about 250ms in DOM rendering - on some slow, crappy, ugly plattforms (not talking about IE6 here, but IE7 and 8 aren't much better in that regard). i recommend using chrome speed tracer extensively for DOM rendering optimization. what is just a little bit slow in chrome is unbelievable slow on IE.