Hello,
I manage to create my account because someone gave me the direct link. I have some problems with the website. I tried the website in IE, Firefox & Chrome.
In IE, the account link from the menu dosn't work at all.
In Firefox I ca see the login window, I clicked "New account" then continue and the "ajax gif loading" appeared but nothing else happened. After 10 seconds the window disapear.
On the games page if I click a screenshot in the thumbnails, over the thumb the ajax gif apears but no screenshot.
Same thing on the Contact Us page. I actualy tried to email you from there but when I clicked the green button the ajax gif appeared again and nothing else.
Any suggestions? I tried this on all the browsers....
Thanks

Actually I just refreshed the forums window and I saw my topic was actually posted.
Right now my "add new topic" window is still open and it's "loading". Check the screenshot.

I'm thinking it is something on your end, either your ISP or something on your PC is goofing up the site. I just hit all the places you did with Firefox and IE (I don't use Chrome) and had no issues whatsoever.

his ISP has nothing to do with the site, other than how fast it might load. Don't make him call his isp over something like this. It's clearly an issue with his computer.

I'm trying to figure out what is causing this problem.
I manage to register because a firend gave me the direct register link.
I'm not a n00b in computers or web programming but I have no other problems on other websites.
Hello,
I found the problem. It was my Ad remover program named AdMucher. I emailed them so they will not filter the website. They are pretty good at fixing the unwanted page breaks.
However in Firefox I still have that problem. Strange... but anyway, it works in Internet Explorer :)

I was about to ask if you had some sort of ad or flash blocking stuff running
Might be an idea to clear your firefox cache too

I talk to AdMuncher guys and they fixed it. Everything works fine now.

While this was an issue with his PC (technically), it was entirely possible that his ISP could have been doing content filtering that would cause issues like this. While I agree, calling his ISP should not be the first step in the troubleshooting process, it should not be blithely removed from the list of "suspects" and should always be an option in case all other "suspects" don't pan out.

typically if they were doing a sort of content filtering, they would say "hey, this page was blocked by us, either due to a request you made or because the page violates our TOS."
the content filtering bit is highly unlikely, I'm not certain what type of scripting their using, but the rendering and how it is handled would be done completely on the end of the browser/computer rather than with how he receives the data.
He was obviously receiving the data it just wasn't being handled properly, if it was a content filtering issue like I said, there would have been a notice from the ISP warning the user, and possibly even logging the event.