How to improve performance of Web 2.0 apps

[Anirvinya]

Hi all,

With the emergence of Web 2.0 applications and popular, the way people use the Internet has quietly changed. Now, these Web 2.0 applications have many typical characteristics, including the possession of rich-client, large pages, the page contains many small projects, a large number of JavaScript code and so on. Given the current browser technology, most of these features will lead to the browser-side performance problems, especially in the long-distance network. So i want to know that how to improve performance of Web 2.0 apps. Please suggest.

[Reegan]

With the emergence of Web 2.0 applications and popular, Internet usage has changed in the emergence of a new trend. For content management, information sharing, communication, teamwork and so on to create a more user-centric approach. From a technical point of view, Web 2.0 applications and did not bring many new technological breakthroughs. However, these applications poses a new kind of Internet usage patterns. Now, Web 2.0 applications have many typical characteristics, including the possession of rich-client, large pages, the page contains many small projects, a large number of JavaScript code and so on. These characteristics would cause the browser-side performance issues, especially in the long-distance network. These performance problems will adversely affect the user experience, but you may not even aware of these problems do exist. As the developers have a good network conditions, these performance issues is difficult to completely exposed. All the best.

[opaper]

Web 2.0 applications are becoming increasingly popular. Many Web sites use Web 2.0 to build, such as Facebook, Youtube and so on. The following is a response time of the browser used to calculate the basic methods:
# Browser, server-side response time = time + time + page loads the browser render time
# Page load time = (number of requests / concurrent number) * delay time + the total page size / bandwidth
# "Server-side time" refers to the server-side processing time spent, for example through the LDAP authentication and retrieve information from the database.
# "Browser presentation time" refers to the browser render the page the time it takes, including the implementation of JavaScript and DOM tree parsing time.

[Zecho]

In a typical Web 2.0 rich Internet applications such as the Lotus Mashup Maker, the browser first sends a request to the server definition format. The definition of response data is received, the browser sends data requests to the server. Then, the browser render the page the user. In this model, there are a large number of small projects that request, such as JavaScript files, CSS files. In long-distance network environment, this will lead to seriously affect the user experience of client-side performance issues. Most files can be cached static files, so if you add the appropriate cache control, expiry and other effects the head the head of the browser cache metadata, it can significantly improve the user experience.

[MindSpace]

you can use Cache-Control for better performance in Web 2.0 apps. Cache-Control is the most important rules. This field is used to specify all the caching mechanism in the whole request / response chain MustTo obey instructions. These instructions are earmarked for the cache to the request or response to prevent adverse interference behavior. These instructions are usually override the default caching algorithms. Cache directives are unidirectional, that is, there is a request response command does not mean that there will be a single instruction. cache-control is defined as: Cache-Control = "Cache-Control" ":" cache-directive. All the best.

[Praetor]

You can also use Apache Roller Weblogger. Apache Roller Weblogger is an open source Web 2.0 Web applications. When the user first visit to this page, it will take about 16 seconds for the browser to display the entire page. If you define the correct cache settings, the majority of resources will be cached to the browser. Therefore, when a user re-visit this page, the page number of requests will be reduced to 22, only about 6 seconds to load. Be greatly improved user experience. All the best.