3 ms·
> The calculation cost and time are so minor and assets so malleable that it can't possibly end up the bottleneck - not when you have ten or twenty widgets, scr
by johnchristopher 13y ago
> The calculation cost and time are so minor and assets so malleable that it can't possibly end up the bottleneck - not when you have ten or twenty widgets, scripts, and trackers loading as well.
No, it can be the bottleneck.
http://mobile.lesoir.be http://mobile.lesoir.be with its 3000x3000 pixels images for a mobile website can make my firefox really sluggish on my notebook.
As far as I can remember there always have been rendering problems with displaying downsized large images on an html page (notwithstanding the bandwidth waste).
- johnchristopher 13y agoI can't edit. I would like to add: it's not as much a problem of displaying large images than displaying large images in <img> with smaller width and height. Interestingly the aforementioned website works like a charm with opera mini running on my feature phone.
- kalleboo 13y agoOpera Mini does the downscaling on Opera's server farm, so your feature phone only gets pictures the exact size of your phone's screen.
- johnchristopher 13y agoI know. I wanted to point out that an inexpensive device experience is better than my full-blown computer* experience. * I know it's an old computer now but it should be able to display pictures on website whatever the scenario.