Response and Update
Here is some additional information:
The reality of the situation is that the server, for the most part, is absolutely fine. The website itself, however, is operating on a level slower than normal. A preliminary report shows this is due to 460 database queries per second being initiated on the database. This means the server is expending all of its resources serving up queries. And while that response is quick, we are on the cusp of what can be considered an overload.
Because the database is using up this much processing power, this makes the web server itself slower to load pages. Those page loads are delayed for delivery for several seconds since so much database activity is taking place. There are some ways for us to solve this problem -- and one way of doing so is to lessen the load on the database. This could be accomplished by identifying the queries per page and trying to lower them by removing unnecessary features.
But before we do that, we are currently working on internal optimizations which may help "lighten the load". There is no danger of the server becoming inaccessible or extraordinarily slow, as we could still serve, in all likely-hood, double the number we are serving today. It would be then that this would become a major problem.
People claiming to see artifacts on the screen or discussing some major, extreme slowdown must be getting a bad route to the website or there is an Internet connection problem to the site. This is a an extremely small, but very vocal minority, which equates to about .01% of the visitors we get on a daily basis. The reality is, anyone with broadband, and not dialup, has probably noticed a small to moderate slowdown of the site. Part of this is because we have doubled the number of features in the last 6 months, and the number of visitors has grown to nearly 1.5 million unique a month.
Rest assured the problem will be solved soon enough.