33 thoughts on “Optimizing web graphics”

  1. For smaller files sizes at higher visual quality:
    Step1 – Use fireworks NOT photoshop (reduces files sizes by half sometimes)
    Step 2 – Shhhh just try it, you'll see.

  2. @sKratch1337 anyone who still uses jpeg is beyond me, and like i said i could care less about the space and the capacity. yes i use photoshop but i still highly prefer PNG over jpeg any day. like i said, quality over space

  3. @thebestcindiella You're stupid, the space / quality ratio is way to low for it to be worth it, just use JPEG and put the compression rate at 10 (If you're using Photoshop.) you won't be able to see it unless you put it under a microscope. But the file size is probably going to be like 2x as small as if you used a PNG file.

  4. @Talk2Luke no its not. its pronounced GIFF. you are .gif files .jif? NO its GIFF and thats how im going to keep pronouncing it. GIFF not JIFF what the fuck this isnt peanut butter. #fuckouttahere.

  5. Vectors always aren't the best solution. Especially for complex and/or huge graphics. The amount of code required could take up more space than a bitmap in some cases.

    Although SVGs are nice since you can infinitely zoom in and never get a rasterized (I think I just made that up) view.

  6. Another tip is always work in vector.
    Don't go near transparency sliders for anything, full, semi (25/75 if you really need to) and 0 only if you do.

    Too much noise in images can lead to bad compression, diagonals can also be a problem, especially if they are uneven.

    Hopefully more browsers add better support for SVG, SVG is sweet.
    And since it can be dynamically generated (xml-based after all), you can compress it even better than the default. (simple substitution compression, repeats, etc)

Leave a Reply

Your email address will not be published. Required fields are marked *