Recently optimized for a personal portal site.
In the traditional sense, this site is all aspects of the Convention. However, as a client-centric Web application, its performance, especially its perceived performance (perceived performance), is often severely constrained by the browser itself. An application that has not been carefully designed and optimized for client-side data access models often leads to the inability to take full advantage of bandwidth and to allow users to wait longer. In other words, its perceived performance need to be further improved.
The goal of this optimization is to break through the browser limit, make full use of bandwidth, improve performance, especially perceived performance and so on. In the next few articles, I will talk about the limitations of the browser and discuss the various ways of this optimization in several ways. Since this personal portal is developed using ASP.net ajax, I will also give some solutions based on ASP.net Ajax, hopefully with some reference value that can be helpful to our friends.
Tools
Based on the principle of seeking truth from facts, we need to use data to speak, so we also need some useful tools. They help us to count the data so we can analyze and optimize it.
In IE, we need to use the HTTP Watch tool to count the information on each request in the page, such as start time, duration length, etc., can easily get detailed data (Figure 1), very useful. And for us, a free edition is enough to use. Free Edition can not get all the information on each request, but we already have the familiar fiddler. We can use Excel to make statistical charts (figure 2) and analyze them.
Figure 1: Access to http://www.google.com statistics
Figure 2: A statistical chart drawn using Office 2007