Web applications: Delays caused by page transitions

Navigating from one page to another in a Web application takes longer than moving from a main window to a dialog box in a traditional application. Delays inherent in navigation add to users' cognitive load because they have to keep context information in their minds while waiting. It also makes their work take longer than they expect.

Delays arise from two sources: network traffic and computation. If the Web server is on a network, especially if the server is distant, it simply takes more time to serve pages to the browser. Furthermore, Web applications typically depend on servers for computation, such as calculating shipping charges or re-sorting a list of names and messages, which adds to the wait for users.

While these delays may seem small, computer users have come to enjoy faster response time than is currently available on the Web. Moreover, users do not know what to expect because there is no way to provide feedback through a progress indicator when operations take a long time to complete.

To help minimize the delays caused by working on a public network, try these techniques:

Create an intranet, where you control the infrastructure, instead of using the public Internet.

Use smaller graphics and fewer pages reduce the time spent waiting for pages to download.

Make navigation clear to reduces errors and overall task time

Navigation in Web applications

1. Introduction
2. Basic navigation
3. Losing users and losing work
4. Separating the browser and the application
5. Lack of context
6. Delays caused by network connections
7. Conclusion

Download the full article (PDF, 52KB)