Fär den här biten tar jag och är lat och citerar mig själv, från en text jag skrev till en diskussionsgrupp en gång.
Some general tips on how to "surf" the web more efficiently:
- Turn off Java and Javascript (and only turn them on when you really want to see a web page that doesn't work without them). You will find that this makes many pages load much faster and causes your browser to crash less.
- Turn off image loading (and load those images you want to see, after the page has already loaded). This will make the page load faster. Often the only pictures people have on pages with mostly text are just decorations, that don't really add anything to the content. This way you don't have to see those decorations.)
Some general tips on how to make fast web sites:
- Don't use unnecessary graphics, sound, Javascript and Java.
- Reduce the file size of the pictures you do use. Most photographs will have a smaller file size (and better visual quality) in the JPG format. Most drawings will have a smaller file size (and better visual quality!) in the GIF format.
- Make sure to add WIDTH and HEIGHT to all IMG tags! (especially those at the top of a page and those inside tables) This can make a page appear to load much faster (the user will experience that the page is faster, even though it really takes just as long to load as before, but in this situation it is what the user experiences that matters).
- Make sure to add good ALT text to all your images (for images that are only decorative you use ALT="" to tell the reader that the image is decoration and not content). This helps the reader to see which images are interesting enough to download, and he/she will then experience a faster page.
- If you are going to put a sound file on a web site, don't make it so that it loads automatically. Instead, make an ordinairy link to the sound file. Example: <A HREF="meow.wav">My cat can sing!</A>. This way the reader has a choice to load or not load (remember, many sound files are huge, i.e. they will take long to download).
- Don't use tables or frames unless it is really necessary. It is often better to "hand code" a page than to use "WYSIWYG" HTML editors, since that gives you "cleaner" and "leaner" code, that often loads faster (depending somewhat on the author's skills, of course).
- Write correct html. Incorrect html will make the browser work harder, which will make the page feel slower. A "validator" (like a "spell checker" for html) can be very useful. You can find one here:
http://validator.w3.org/Veronica Karlsson