Basic Tips for the site to reduce the load time

Home

Basic Tips for the site to reduce the load time

When the collection of some pages load times, and the effective bandwidth for real users from around the world, you can try out changes that will improve their times. The measure the difference and keep all of which offer significant improvements. Try some of the following:

Use HTTP keepalives external objects. Otherwise, you can add another back and forth to make a second TCP three-Way Handshake for each HTTP request. If you have a concern worldwide server connection with the limits, set a timeout keepalive something short as 5-10 seconds. In addition, we expect you to serve static content other than the dynamic Web content. Thousands of links to open to moving a static image, a web server can be done 10 megs of RAM the total, while your main web server can easily eat 10 megs of RAM.

Load fewer external objects. Taking into account the requirement of management, bigger picture, only to load faster than the two smaller half its size. Figure how to combine the world the same one or two of the javascript files, and one or two external styles instead of many people, even if you have more, try the assessment, as far as their publication. If the user interface used in dozens of small GIFs the whole place, to consider the transition from the much cleaner CSS-proposals, which probably do not need so many photos. Or, download all of your common UI photos one application using a technique known as the “CSS sprites.”

If users regularly load of a dozen or more uncached or uncacheable objects on the page, you should consider the breakdown of these objects for more than four names of the host. This usually means that users may not be so many unresolved 4th connection with you. Without the HTTP pipelining, is a result of their application latency drop from an average of about 1 / 4 of what it was before.

When you create a page pictures evenly spread over four hostnames is easy to transport in the hash function, such as MD5. On the other hand, has all the signs load of goods http://static.example.com/, the establishment of four servers (for example, static0.example.com, static1.example.com, static2.example.com, static3.example. Com ) And two-bit graphics MD5 way to choose which of four hosts must be accompanied by tag. Make sure that all aspects of the same server, a consistent reference to the same file URL, or you can eventually forced to the cache.

Would you be so kind to each other hostname adds a surcharge to the overhead DNS lookup, and additional TCP three-Way Handshake. If users have switched on or daisy-chained page loads of less than dozens of objects, they see no benefit from increased parallelism and the site can actually load more slowly. The benefits to only appear on the site, with more objects. Be sure to measure the difference between the users are seen if you choose this.

The idea is relatively simple: When you create a page that give the browser a bit of information in addition to what had been the page, which you’ll be sent. If the viewer is asking the same page, once again, that this information back to you. If the matches are, what you need to send, you know, that the browser has already been copied and will send a much smaller 304 (unchanged), rather than responses to the site again. And if you’re smart about what you attach to ETag, you can bypass the most general queries, which would have gone to produce sites.

To minimize the size of an HTTP request. Often, cookies are domain-wide, which means that they are also unnecessarily sent to the browser, and every picture at the request of this area. What could have been a 400-byte at the request of a picture can be easily converted to 1000 bytes or more, when you add the cookie headers. If you have a lot of uncached or uncacheable objects in the page, and a large, broad domain cookies, use a separate domain to host static content, and make sure that never any cookies in it.

To minimize the HTTP response to the size of thanks to gzip compression in HTML and XML-based browsers, which support it. For example, the 17th of paper you’re reading, take 90ms at full bandwidth, which is connected to the user’s 1.5Mbit DSL. Or, it will take 37ms, when the compressed 6.8k. This is 53ms out of the entire page load time for a simple change. If HTML is greater and unnecessary, you’ll see even more improvements.

Use Firefox, a realistic context, the net amount is reflected in graphic timeline, what to do after the page loads. This shows Firefox, which will have to wait for one HTTP request to supplement prior to the next page and storage is growing every object loaded. YSlow extends Firefox offers tips on how to improve the effectiveness of your site.

Safari offers a tip for the working group has been hidden features, the browser that provides some information about the timing. Or, if you’re familiar with the HTTP protocol and the TCP / IP packet data, you can see what happens through the tcpdump, ngrep or necessary. These instruments are indispensable for all kinds of network debugging.