The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Well it's here now ... so start webbing and technicalling chatting ...
Google 'exposed'
End of Windows?
Not all surprising, but worthy of a read :¬)
If you look at Freeola.com that has already been pretty optimised but you're saying you still get the occasional pause?
The stylesheet http://chat.freeola.com/css/main.php?1181838671 was loaded as CSS even though its MIME type, "text/html", is not "text/css".
and there's more ...
Google's Site Check mentions JS - lots of Facebook...
[s]Hmmm...[/s]
The issue with logging in to MyFreeola is not the same. I think that is more down to various database connections that are made, some of which are sometimes slow. I think the MyFreeola issue is being looked into but the solution is a long term thing to code up.
It looks like you posted your own IP there - so you may want to edit things?
FWIW - I also sometimes see delays loading Freeola's pages.
Nothing to put my finger on since you started this thread though!
I also (sometimes) see longish delays logging in to MyFreeola - waiting for the page to load. I'm usually using FF for this to manage my account.
Today the Chat pages don't seem to be very snappy in XP/IE8 for me, much better in Chrome/FF. I didn't see this yesterday?
Sometimes I'm seeing *waiting for* the Facebook plugin to load.
It's worth saying my Freeola connection is fine with my normal IP Profile etc.
[s]Hmmm...[/s]
EDIT: Now disappeared ;¬)
Also, if/when this happens again, could you try pinging one of the image host that Firefox is hanging on.
It's happened again, so I noted each 'hanging point' and then stopped each page loading and refreshed it ... the ping results:
images.freeola.co.uk
Reply from 93.174.140.110: bytes=32 time=15ms TTL=52
Reply from 93.174.140.110: bytes=32 time=14ms TTL=52
Reply from 93.174.140.110: bytes=32 time=14ms TTL=52
Reply from 93.174.140.110: bytes=32 time=15ms TTL=52
Finished
images5.freeola.co.uk
Reply from 93.174.140.115: bytes=32 time=14ms TTL=52
Reply from 93.174.140.115: bytes=32 time=14ms TTL=52
Reply from 93.174.140.115: bytes=32 time=14ms TTL=52
Reply from 93.174.140.115: bytes=32 time=22ms TTL=52
Finished
images4.freeola.com
Reply from 93.174.140.114: bytes=32 time=14ms TTL=52
Reply from 93.174.140.114: bytes=32 time=19ms TTL=52
Reply from 93.174.140.114: bytes=32 time=15ms TTL=52
Reply from 93.174.140.114: bytes=32 time=14ms TTL=52
Finished
profile.ak.fbcdn.net .... also a cause of hang
Reply from 23.63.98.251: bytes=32 time=13ms TTL=56
Reply from 23.63.98.251: bytes=32 time=11ms TTL=56
Reply from 23.63.98.251: bytes=32 time=11ms TTL=56
Reply from 23.63.98.251: bytes=32 time=11ms TTL=56
Finished
No blockage this end, it would seem.
EDIT: The last one mentioned has always been a pain! The only time it wasn't was when I used AVG Do Not Track!
EDIT: Add images6 to the list above and other facebook links ... which have always been a pain and an uneccessary addition to the site!
We haven't changed anything this end so it does seem like a weird intermittent network related issue somewhere.
Maybe enabling email notification on a 'Security event' may throw up something, page 58 of: the user manual.
Also, if/when this happens again, could you try pinging one of the image host that Firefox is hanging on. If that is not pingable then it is probably blocking going on your end. We don't do any kind of blocking our end.
What's the model and version of your router and does it have the latest firmware installed?
I'm think the router may be the problem more than the server or website setup as I don't think we've had any other report of this (tempting fate!).
Just checked on my Firefox and all seems fine.
Netgear N150 wireless ADSL2+ Modem router DGN1000
Firmware: V1.1.00.45_ww
ADSL Firmware Version: 3.5.2.9.0.1
Just checked firmware and the latest is installed ... what next?
EDIT: Just logged back onto Freeola Home page and the router interface...no problem, no hang! Router Logs seem to have been cleared, as the only entry was Router start up yesterday!