Current time: 11-25-2020, 07:34 AM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Manchester so much to answer for
01-15-2016, 08:25 PM (This post was last modified: 01-15-2016 08:59 PM by trevor_mccombie.)
Post: #3
RE: Manchester so much to answer for
Thanks Anton,

Agree in principle re: your "worst case" scenario and IE11.

Unfortunately running the test from Dulles VA still shows the site taking 13.886s on Chrome. So in this case Chrome is the "worst case"!!

I should be clear I'm not saying that this is the fault of where I'm running the test from. I'm more leaning toward some issue with HTTPS but I'm not sure what.


::::: ::::: ::::: ::::: :::::


So I got a little obsessive after my initial post above and decided to take a little world tour. It might help if I mention I'm based in Edinburgh, Scotland UK to put this into some sort of perspective.

The following we're all ran on 5x, Chrome with a Cable connection. Remembering I'm based in the UK its surprising Ireland comes out worst. I should also make it clear that in reality on viewing the page load in Chrome it takes no where near these times to load.

Ireland - EC2 61.331s
Shanghai, China 48.645s
Australia - EC2 46.141s
Amsterdam, NL - Go Daddy 27.593s
Moscow, Russia 21.163s
Johannesburg, South Africa 16.785s
Ashburn, VA USA - Yottaa 14.927s
Dulles, VA 13.886s
Frankfurt, DE 13.629s
San Francisco, CA USA - Yottaa 12.174s
Sydney, Australia (Servers Australia) 11.681s
Brazil - EC2 9.2s
Hong Kong, China 8.869s
Petah-Tiqwa, Israel 6.938s
Montreal, Canada - Akamai 4.969s
New York, NY USA 3.531s
Brussels, BE 3.517s
Paris, FR 3.418s
Prague, Czech Republic 3.104s
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: Manchester so much to answer for - trevor_mccombie - 01-15-2016 08:25 PM

Forum Jump:

User(s) browsing this thread: 2 Guest(s)