This article provides performance tips that improve perceived time more than actual time. Two or three are founded on the principle of setting appropriate expectations.Measuring the time that passes while the system performs some task gives us a good indication of performance, but there’s more to the story. There are four types of time we… Read the full post

Whew! That was a long series. But we’re finally at the end. Let’s wrap up with the top ten things to consider when our thoughts turn to website performance. These are our top ten best practices.There are many performance tips out there, but performance may be affected more by how the development team thinks about… Read the full post

So far, this series presented the details of all the things that happen after a user clicks a link to retrieve a new web page. It purported to follow the details chronologically, but in truth we know that cannot be true. If all the processes we discussed were to happen consecutively, the web page would… Read the full post

The last episode of this series completed what we set out to do – detail what happens after a simple little click on a link. At this point in the series, the page is now fully loaded.Many articles stop here, but there’s so much more to the story. If we define poor performance as the… Read the full post

This series has been following the chronological progress of a click on a link. The click was converted to a request, sent to the server, and processed by the server. The server created a response and sent it back to the client, where the client-side script executed. Today’s episode tells how the output from the… Read the full post

This series has been following the progress of a request and its response. The request was initiated by an end-user’s click on a link, which signified his request for some web page to be downloaded and presented to him. So far in this series, we’ve seen the back-end (i.e., the server) fill the request and… Read the full post

When we left off last time, our hero had bravely traversed the Internet and found his way back to the client machine. What courage! What tenacity! What a component!Now that the component has arrived at the client machine, it must make its way up the protocol stack, which is the subject of this part. Climbing… Read the full post

At the end of Part VIII the user’s request had been served, but had only made it to the bottom of the protocol stack in the server machine. This part describes the next step, the journey through the Internet from the server machine to the client machine.Part III described this journey in the opposite direction.… Read the full post