QUOTE(Vue @ Apr 15 2007, 11:12 PM)

Hello there.
For this "experiment" of mine, images were saved along the exact following:
- Save for Web...
- Select .GIF
* I used the Google (Australia) logo. I randomly used the slice tool and ended up with 8 slices. The files added up to
29.7 KB.
* Then I used the slice tool again to slice the image into...one slice.

This image added up to
7.29 KB.
(With defaults settings for "Save for Web..." under .GIF when saving for BOTH.)
Oh and go ahead and rebut my claims. This topic is open for discussion!

I think I poorly did this experiment, so hopefully someone can try it.
Further:
* Image slicing is not necessary for image maps.
*
http://yoursite.nu/mbtopic.php?id=274* (I've read somewhere that it is also not necessary to slice images for link rollovers, hopefully the pros at Astahost can help me haha)
Well in some instances using slices help, because different forms of imagery can be compressed separately
in different ways for maximum compression. For instance, with flat, non-gradated colors, you could use GIFs
optimized with pallets limited to only a few colors; whereas, with more photographic/rendered/gradated images
a JPEG compression would be more fitting. So if you split the flat colored-shapes from the photos, then you
would have a faster loads page then if you didn't slice. Also, some people use slices so that the viewers don't
have to wait for one big image to load. When see little parts filling in and loading, they might be more likely
to stick around and wait for the page to finish loading. It is the same idea as with interlaced/progressive images.
They load in layers of quality so that the viewer can see that something is happening, even if they are a little
larger in files size than the non-interlaced images.
Reply