Given the ever-increasing speed of the average network connection, I am not inclined to think that page loading time is of great concern [ducks!]; Actually, itβs much more useful to think about what you are trying to achieve using the resources that you have at the end: for example, limited bandwidth? Then the desire for more severe compression is not difficult. Will the graphic content of the site expand, ensuring that the cost of space on the server increases over time? Then the desire for more severe compression will delay this cost. Is this an art portfolio? Then - yeah! - Compression artifacts in working with the probe can be really desirable! Are you trying to flog a game? Then the screenshots should probably be ultra-clear.
In the general case, I would repeat what was said, although perhaps in a slightly different language: for furniture for sites, which are usually computer-generated and will be cached for reuse between pages, tend to png; For site content that will often be page specific and probably large and complex to mask lossy compression, lean towards jpg.
With a special link to switching to png, where you decide it is appropriate, run everything through PNGCrush for granted - otherwise they will not be displayed with the colors that you expect in each browser, and the overall quality of your design will decrease .
Sledge Nov 09 '09 at 1:26 2009-11-09 01:26
source share