|
Site MapYour Current Location is in Yellow Graphics
|
GraphicsMany people discover, to their dismay, that the nifty photos, animated gifs, cartoons, buttons, etc. they have placed on their page take a very long time to load. Many do not discover this until a friend visits the page and points it out, because the page loads fine for me. Actually, what is loading at a brisk clip is the cached version of the page, so the creator is getting in a few moments (from his own hard drive) what will take 15 or 20 minutes to load over the phone line. Now, some web page creators, when confronted with this fact, will simply take the attitude that this is great art, and people will just have to wait. News Flash! They wont. So what do you do? How do you get graphics without the long wait? The answer is: know your craft, apply your knowledge, create in your head before you put it on the page. At least have a rough idea of what you want to do. A page consisting of 16 poses of your goldfish accompanied by brief cute captions is not likely to capture the hearts and minds of your visitors. Use graphics sparingly. Make those bytes count! Another consideration: animated gifs are generally cool the first time you see them, and mildly irritating thereafter. A good animated gif can be a lot of fun even after the first viewing. But a dozen animations on a site more likely will only make the visitor dizzy. Use animations sparingly or not at all. By the way, this also applies to Java gewgaws. I've seen pages that consisted only of a title and three or four of those undulating water reflection things. Booorrrring! Actually, what I said in the last two paragraphs points out from another perspective the biggest challenge to writing a good webpage: creating content. Sometimes that requires research, sometimes it requires real writing skill. But the content is what makes a page worth visiting. Now, how to tame those graphics files? It depends on the graphic. The file size of any graphic can be reduced by simply reducing its physical size. On web pages, a rule of thumb is that 72 pixels will be about one inch of screen space on average this will vary by screen size and resolution. I point this out because while a photo with a 1200 dpi resolution may look great on paper, it will be way too large for most web pages, and the file size will likewise be way too large unnecessarily. Those 72 pixels will always be the same width on the screen, so a higher resolution graphic (more dots or pixels per inch) will simply take more space on the screen. When scanning or sizing your graphics, think in terms of pixels. For example, if you want the picture to cover half the width of the screen, use about 400 px for the width. You can also reduce the size of a graphic by trimming away unnecessary background. You can often reduce the file size of a graphic by 40K by simply doing some judicious cropping. These comments are not meant as a thorough tutorial on resizing graphics, but simply as starting points for you to explore as you experiment with resizing your graphics and taming them for use on your web page.
If you lack the patience or the experience to reduce your graphics, you could try the graphics editors available online. Some charge fees, others will give you a free trial, and still others will do it all free. I personally prefer GIFCruncher (and the associated JpgCruncher). If you want to see the difference between the original and reduced versions of a photo, look at this example. Here are some of the better known sites: Graphics Optimizers
Graphics Editors free trial or shareware
[Note: If you are having no-show graphics problems, see the HTML FAQ]
Copyright © 1999 Carlton Higginbotham, Meade Street Productions.
Last updated GMT
|