Quote - ok lets take this futher with Diagnostic Data:

.....

Tracing route to www.renderosity.com [66.18.106.204]

.....
.....

but..... page load time .... 18.995 seconds.... (the above trace (with timeout) took 6 seconds)

anyone wanna explain the disparity of 13 seconds?

One possibility with your example is that you are comparing page loading at one address with a trace route to another.

A tracert to market.renderosity.com at the time of worse (apparent) site response will be interesting. Having said that, Nicholas has already intimated that page generation at the server is the key issue. Having said that, it's been really flying today (from here in the UK) so far, with user numbers ranging from 600ish to 1200+. So it doesn't appear to be site traffic that's the problem.

Maybe take a look at which server Solitaire and Tetris are stored on at Bondware HQ. ;-)

.