5 ms·

You could just slice it into multiple JPGs. It's probably even better for parallel download.

• gokhan 15y ago
  Better? Wrong. Please read "Minimize HTTP Requests" here: http://developer.yahoo.com/performance/rules.html http://developer.yahoo.com/performance/rules.html
  • wisty 15y ago
    If you use domain sharding you can get more parellel downloads on older browsers which reduces the problems some due to more requests (parellel request limit on old browsers and unneeded cookies for static resources, but theres still overhead), but that's a separate issue. It's best to avoid the problem altogether by minimizing HTTP Requests (as you suggest).
  • huxley 15y ago
    That's a great rule for general purposes, but it's intended for situations where you have lots of small assets that you are asking the client to download. In this instance we're talking about 2 megapixel images, so the extra HTTP requests are not even going to register in the mix. With modern browsers pulling down 6+ parallel downloads, breaking the image up might make plenty of sense.
  • rorrr 15y ago
    It's not wrong. If you have only a few slices, they will load in parallel in most browsers.
• apinstein 15y ago
  Well we already slice our images, and even those slices are too big. We were annoyed to have to maintain another set of files just for the iPad. So we just use a smaller (and blurrier when scaled up) image at the moment. I was hoping they would just open it up :)