Reducing the number of HTTP requests in your page is the place to start. Inline images are not yet supported across all major browsers.

Combining inline images into your (cached) stylesheets is a way to reduce HTTP requests and avoid increasing the size of your pages. This can increase the size of your HTML document. Inline images use the data: URL scheme to embed the image data in the actual page. Using image maps for navigation is not accessible too, so it's not recommended.

Defining the coordinates of image maps can be tedious and error prone. Image maps only work if the images are contiguous in the page, such as a navigation bar. The overall size is about the same, but reducing the number of HTTP requests speeds up the page. Image maps combine multiple images into a single image. Combine your background images into a single image and use the CSS background-image and background-position properties to display the desired image segment. Combining files is more challenging when the scripts and stylesheets vary from page to page, but making this part of your release process improves response times.Д¬SS Sprites are the preferred method for reducing the number of image requests. But is there a way to build pages with richer content while also achieving fast response times? Here are some techniques for reducing the number of HTTP requests, while still supporting rich page designs.Д¬ombined files are a way to reduce the number of HTTP requests by combining all scripts into a single script, and similarly combining all CSS into a single stylesheet. One way to reduce the number of components in the page is to simplify the page's design. Reducing the number of components in turn reduces the number of HTTP requests required to render the page. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. Pack Components Into a Multipart DocumentДЁ0% of the end-user response time is spent on the front-end.

Simple dns plus redirect loop