can we Make our site as backward compatible ?.

* For example, if you use Flash, and you can make something that works with the Flash  don’t add some little cosmetic feature that requires you to save it as a file that only works with Flash
* Sometimes even if it can be done slightly more effectively utilizing features only available on the latest browsers, it is better to compromise and make a page that works for a wider audience.
———————————————–
can Make our site as fast as possible.

* A. Make fast-loading pages.
o Keep the size of the HTML file to a minimum.
+ Eliminate everything that doesn’t show on the surface of the page. Eliminate multiple spaces, returns and tabs in the HTML code. Remember that any amount of “white space” is reduced to one space on the surface of the page.
+ Remember that color changes, font size changes and tables add to the size of the file. Consider not using these.
+ Be careful when using HTML editors. Most, maybe all, insert a lot of unneeded duplicate code, resulting in files much larger than necessary. If you learn enough HTML to edit out the “junk”, you can often more than halve the size of the file.
o Make your pages cache-friendly.
+ Design pages that can be cached, both by Internet or proxy cache and local cache.
o Avoid other things that slow down the loading of your pages.
+ Avoid CGI, SSI on pages that can be static pages. Your page will be faster. This also allows the pages to get cached which may allow the visitor to get your page even faster.
+ Don’t use images or use only a few small ones. Using an image for the page title is not so bad. However, it is so easy to add images to pages, that inexperienced writers often put in too many.
—————————————————————————-
# B. can we Make fast-displaying pages.

* What makes a visitor wait is not only the amount of time it takes to download, but how long it takes for the page to display.
* Traditional, straight-forward formatting allows visitors to read the top of the page as the rest of the page is downloading. Full-page table formatting and frames cause visitors to wait.
* Remember that what may seem acceptably fast for you on your computer may seem painfully slow on a less powerful computer.
* Avoid multi-column full-page table formatting. This includes pages with a column on the side for navigation buttons. The problem is that your page will seem to stall as the computer is waiting for the rest of the page to come in.
* Include the HEIGHT and WIDTH code for all images. This way people can be reading your page while the images are still loading in.
* Remember that the more HTML formatting there is, the longer it will take for the page to layout. Using many color changes and font size changes will require more time for the computer to layout the page.
* If you feel that you must use SSI or CGI to put a page counter, a randomly-selected image or randomly selected text on the page, put it at the bottom of the page, so visitors can be reading your page while waiting for the delay caused by SSI or CGI.
* Be careful not to include too much “navigation.” Some poorly-designed pages devote a higher percentage of their file size to “non-content” navigation and advertising than they use for presenting “content.”

# C. can we Make your site fast to use.

* Don’t make your pages too large. Don’t make your pages too small. If pages are too large, visitors must wait a long time for the pages to load in. If the pages are too small, visitors spend a lot of time clicking links and reconnecting to your server to get the next page.

Bookmark To: