IS THE FORUM WEBSITE ON A GO-SLOW?

Other conditions
1

It seems to have taken me ages to try and post anything over the past few days as it can take up to five minutes to accept one word of typing.

Has anyone else encountered this strange phenomenon?

 

2

Seems fine to me, archemedes!

But when you PING the server I am losing all packets of data! 100% loss!!

3

not so far 

4

Okay, I got a very result from doing a Trace Route.

Just after Leicester and before Birmingham it timed-ouit twice on Virginmedia's Network.

Then you can see all the Time-Out Requests!! There's loads, looks like Network Congestion to me.

5

Network congestion or maintainance might explain it.

 

6

There is definitely a problem.

I just got this report:

packets transmitted  9

received  0

packet loss  100 %

time  8018 ms

 

7

is it the site or your server. 

8

i am not having anything problems i am with talktalk. and useing google chrome

9

I ran a few tests to the site, I don't know if you're still receiving a long delay but there is a big problem before a page renders, this is what I am seeing:

Time to First Byte: A red "F" = Bad

First Byte Time (back-end processing): 0/1003458 ms

First Byte Time: ms Target First Byte Time

Cache static content: A Yellow "C" = not too Bad, could be improved.

The strange thing is the main patient.info website is on a server in Northern Ireland. Yet, it has to make many requests to the USA for Facebook, Twitter, Google Ads, DoubleClick, UserVoice and even custom Fonts from Google, in fact most requests are from overseas. So, last night if Network Congestion was high then we would see pages slowly rendering.

What I do not understand is why the main server is in Northern Ireland?

The time to first byte though is very slow compared to most of the readings I looked at.

10

Well surprise surprise another one of those little mysteries in life.

Without warning or explanation the website started working again for me.

I doubt if the fault had anything to do with the website (although they very graciously did look into it for me), so I expect it was one of those little network weevils chewing its way through an exchange somewhere.

Who knows?