Images make pages slow; by using them you are adding http requests and files that need to be downloaded. The only time I would suggest it is for logos, which technically are text but not the type of text I’m talking about. Menus should definitely not be graphics.
Images are HTTP requests that slow down rendering and should be minimized. Unless your HTML document is something as primitive as an HTML email, images should not be used for layout. Replace corners, single pixel spacer gifs, shadows, gradients…etc. with CSS3. Very complicated and detailed patterns can be created with CSS.
If the images cannot be replaced with CSS — that is, if it absolutely must be a graphic — collect images into image sprites or consider using using a font face as a library of icons.
Google Analytics or some other web analytics software should be included and used. The priority of this item depends on the type of site, but it is essential for most.
PNG image format was created to improve upon and replace GIF images; they compress better in most cases.* Additionally, there are patent issues around using GIFs.
We suggest PNG-8 for non-transparent images, PNG-24 for transparent images, JPEG for photos, and GIF for animated web graphics.
*An image would need to be very small for GIF to be the better choice.