Interesting design concept - but a horrible implementation of it.<p>You can't just go and load a thousand divs and not expect a wide variety of performance issues across all the different platforms.<p>You need to have a tile manager or something behind the scenes the same way that Google maps does, especially when targetting smaller consumer devices with limited hardware specs like tablets and phones.<p>* iOS5 - with an iphone 3gs (laggy to the point of being unusable)<p>* iOS5 - with an iphone 4 (laggy to be the point of being unusable, unless your patient). I don't have an iphone 4gs to test on, but I suspect it might be more on par with ipad 2 performance. The differences could be to do with retina display vs non retina display as well I suppose.<p>* iOS5 - with an iPad 1 - roughly same performance as an iphone 3gs - crappy<p>* iOS5 - with an iPad 2 - not too bad (but thats because of the gpu tile rendering in safari going on behind the scenes i suspect.<p>* Firefox 15 on a quad core i7 imac - massive ram spike, and crazy lag with the scrolling<p>* Chrome on a quad core i7 imac - no problem.<p>I'm not even going to bother trying this out in IE!<p>edit: Latest version of Opera has provided the poorest results yet, it keeps lagging and pausing and reloading the images after they have already been loaded (didn't check to see if it was actually downloading them again though)