We keep very good information on how long our pages take to render. In fact, you can see for yourself how long it took our server to make the page you're looking at.

View the source on any page and scroll all the way down to the bottom. You'll see a line like the following:
<!-- Build Version: rel-34-8 Build Date: 20080805144858 Server: b7,438 -->

That last number (438) is the time in milliseconds (thousands of a second) that the page took to create. 1000 is 1 second, so 438 means less than half a second to create the page. That's just on our end, though. It will take more time for your computer to make the request and for us to send you the response, but we do everything we can to minimize how long it takes to create a page.

"Slow" to us is more than 1.5 seconds. We have very few pages that take more than 1.5 seconds to generate. What's New and the Members pages on really busy sites are two of the biggest.

When it comes to editing pages, though, the real benchmark is the JavaScript performance of client computer, OS, and browser. It has very little to do with how our servers are performing. If editing a page seems very slow, there's probably other processes running on your machine that are slowing it down. Try restarting your browser or even your computer. I find that usually speeds things up for me.

Frankly, IE7's JavaScript performance is terrible compared to Firefox 3. I notice a difference every time I switch between the two.

1  out of 1 found this valuable. Do you find this valuable? Do you?