It was slow for me this morning too - I restarted the application server and it seems to be a bit better now.
The problems most people were experiencing for a week or so, I believe were network related - they didn't affect everyone, just certain sets of users. Once the network congestion was fixed, it started working well again for them.
The way the internet works is that there are many different paths that network traffic can follow to get from your computer to the server (and back again with the website data!).
It is up to your ISP to determine which path they send your web requests along - and then subsequent network providers along that path then choose which is the next path to choose to continue the journey to the server.
Sometimes there is a problem with part of the path along the way - perhaps too many people trying to use that same bit of path at the same time; or perhaps there is a problem with that part of the path and it's really slow to move along it.
When that happens, it can take a long time for traffic to get through that segment of the network - and sometimes traffic is forced to take an alternative path which is much longer. Either way, the end result is that it takes longer to get the data back from the server and the site seems really slow to load.
It can take a while for network providers to track down the exact problem with the network - sometimes it's as simple as rebooting an overloaded router, other times, it could be something more serious such as a cable being broken causing too much traffic being sent down alternative cables, causing congestion and other issues.
So while other people were experiencing problems with getting data from the website, the path that my ISP had chosen to get traffic to and from the server happened to be working fine - which meant that I didn't see any of the performance problems that other people were experiencing. If it were a problem with the server, everyone (including me) would experience it - but network related problems can be isolated to a subset of users.
I will also note that the server which we run ZooChat on is currently in Tokyo, Japan. Depending on where you are geographically located - you might find performance varies because of the distance your traffic has to travel to get there.
My ISP actually as direct network connections to Japan, so I generally get very good speeds between my computer and the servers. However, I know that some ISPs in Australia route their traffic to Japan via Singapore, and others go via Hong Kong.
I know that my next-door neighbour uses an ISP which happens to route his traffic from Sydney via Perth, Singapore and Hong Kong - so it takes considerably longer to get data from Japan than it does for me, even though our phone lines connect to exactly the same telephone exchange!
I've also seen traffic to Japan routed via the US, which means two hops across the Pacific - that really slows things down too.
A lot of network providers are optimised for routing traffic via the US, and the vast majority of websites are generally hosted in the US - so if you compare ZooChat in Japan to other websites you regularly visit, you might experience different performance.
Ahh - the joys of running a website
