The most commonly encountered caches on the Web are the ones found in a user's Web browser such as Internet Explorer, Mozilla and Netscape.
When a Web page, image, or Java Script file is requested through the browser each one of these resources may be accompanied by HTTP header directives that tell the browser how long the object can be considered "fresh," that is for how long the resource can be retrieved directly from the browser cache as opposed to from the origin or proxy server.
As a Web site or application acceleration strategy, its chief benefit is that the technique can provide substantial reductions in network payloads without requiring any additional processing on the origin server.
Source code optimization should be implemented as a pre-deployment step through which all additions and changes to the front-end source code (including markup, style sheets, and client-side scripts) normally pass before being uploaded to the "live" production site or application.
This highly aggressive optimization approach can lead to average savings of 20 to 30 percent in Java Script files and as high as 70 percent in tested, "real world" cases.
A sensible objection to aggressive source code optimization is that it diminishes the readability of the code when one "views source" in a Web browser.
With a large enough budget for heavy infrastructure improvements, any server's connection to the Internet can always be improved.
These basic strategies, which all avoid expensive hardware solutions in favor of software and business process enhancements, include: We assume that our typical reader is responsible in some way for development and/or management of a Web site or application running on one or more Windows servers with Internet Information Services (IIS) and that he or she has an interest in improving its performance as much as possible without deploying additional hardware (such as dedicated acceleration appliances) or services (such as Content Distribution Networks).As we examine each strategy, we will explore the potential benefits to a variety of different Web sites and applications in terms of three vital metrics: We will suggest relatively inexpensive software tools that will leverage common Web standards in order to maximize hardware and network resources, thus improving Web site and application performance while lowering the total cost of ownership of Web infrastructure.The most valuable measurement of Web site performance from an end user's perspective is the amount of time needed to display a requested Web page.Since the browser represents the cache closest to the end user it offers the maximum performance benefit whenever content can be stored there.When a browser makes an initial request to a Web site — for example, a GET request for a home page — the server normally returns a 200 OK response code and the home page.