Is anyone here with Telecom broadband having trouble visiting some websites?

Forums › Spark New Zealand (including Skinny and BigPipe) › Is anyone here with Telecom broadband having trouble visiting some websites?

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | ... | 10

72 posts

Master Geek

#453055 29-Mar-2011 10:24

I was so curious that if we view the websites on IP address rather than domain names.

For example, through Vodafone DNS servers

www.facebook.com resolves to 66.220.146.32
arstechnica.com resolves to 75.102.3.15
guardian.co.uk resolves to 77.91.248.30

If you access those IPs dirctly on a web browser on a Telecom connection, what would happen?

The caching server are only caching contents based on domain name, right? If you can't even access websites based on IP addresses, it must be a network congestion rather than a DNS problem?

AliExpress

Shop now on AliExpress (affiliate link).

caldazar

459 posts

Ultimate Geek

#453116 29-Mar-2011 12:36

I'm finding any websites loading fonts from Typekit.com can be extremely slow. Sometimes with loading times of over a minute to download the fontset.

Depending on the browser, if Typekit is used by the website you are visiting, the page will stall and wait for the fonts to be downloaded before you can view any text.

booleanvalue

27 posts

Geek

#453119 29-Mar-2011 12:43

Thats interesting. Do you know if FF3 and 4 handle this in the same way? I've found FF4 for OSX to be incredibly slow at loading some pages, to the point of ridiculousness and that could be the cause perhaps...

Decal

219 posts

Master Geek

ID Verified

#453139 29-Mar-2011 13:56

Ivor:
If you access those IPs directly on a web browser on a Telecom connection, what would happen?

It depends on how the website is hosted if its the only website associated with that IP then it will load. But if there are multiple domains on the host then it will load what is ever set as the default (if set) because the server reads the header file sent from the browser to determine what page it should send back

caldazar

459 posts

Ultimate Geek

#453148 29-Mar-2011 14:15

Thats interesting. Do you know if FF3 and 4 handle this in the same way? I've found FF4 for OSX to be incredibly slow at loading some pages, to the point of ridiculousness and that could be the cause perhaps...

Firefox is less affected. Firefox renders the website using standard fonts first, while downloading the webfonts. Once the webfonts are downloaded Firefox changes the fonts. So sometimes the website looks weird and then a second later (assuming the fonts download quickly) the website flickers and looks good with the correct fonts.

Safari on the other hand, when I tested this morning was stalling the website until the fontset downloaded.

Although... in saying that.. Firefox can be made to wait just like in Safari, so perhaps on the sites you are visting, the website could be setup this way.

Ivor

72 posts

Master Geek

#453150 29-Mar-2011 14:15

Decal:
Ivor:
If you access those IPs directly on a web browser on a Telecom connection, what would happen?

It depends on how the website is hosted if its the only website associated with that IP then it will load. But if there are multiple domains on the host then it will load what is ever set as the default (if set) because the server reads the header file sent from the browser to determine what page it should send back

Yeah u'r right while these ones should be delicated/default sites on those servers (i tried them)

www.facebook.com resolves to 66.220.146.32
arstechnica.com resolves to 75.102.3.15
guardian.co.uk resolves to 77.91.248.3

Facebook shouldn't be on a shared hosting server :)

Decal

219 posts

Master Geek

ID Verified

#453288 29-Mar-2011 21:45

Ivor:

Facebook shouldn't be on a shared hosting server :)

I think its because its shared over many servers to reduce loading and such

LAC

107 posts

Master Geek

#453851 31-Mar-2011 16:23

I can confirm this happens to me from time to time. And using OpenDNS.

eXDee

4032 posts

Uber Geek

Trusted

#454891 3-Apr-2011 19:47

Still typically getting 10+ second page load times, particularly from Wikipedia. A direct link to a en.wikipedia.org page it took 20 seconds waiting for the server. Browser is chrome.
If i load it through coral cache it takes about 3 seconds which is pretty snappy for coral.

Unsure whether to log this with telecom or not, do they already know about it? I have a feeling if i contact their support desk they will want to put me through the usual speed complaint checklist. Which isn't an issue - 20mbit line sync, 200m to the cabinet, central splitter installed, broadcom chip modem that's very stable, 12ms ping to auckland, 16mbit on speedtests.

bnapi

92 posts

Master Geek
Inactive user

#454895 3-Apr-2011 20:05

eXDee: Still typically getting 10+ second page load times, particularly from Wikipedia. A direct link to a en.wikipedia.org page it took 20 seconds waiting for the server. Browser is chrome.
If i load it through coral cache it takes about 3 seconds which is pretty snappy for coral.

Unsure whether to log this with telecom or not, do they already know about it? I have a feeling if i contact their support desk they will want to put me through the usual speed complaint checklist. Which isn't an issue - 20mbit line sync, 200m to the cabinet, central splitter installed, broadcom chip modem that's very stable, 12ms ping to auckland, 16mbit on speedtests.

Yes please log with telecom. my friend is having the same issue with wikipedia,facebook, etc. My friend already logged his fault with telecom so the more people that log it the better.

eXDee

4032 posts

Uber Geek

Trusted

#454898 3-Apr-2011 20:16

Does anyone know if theres a better way to do it than the helpdesk? I don't want it to just be dismissed as a generic speed complaint which i know they get a lot of due to peoples bad lines etc.

Logged it here in case it helps.
http://www.geekzone.co.nz/fault.asp

eXDee

4032 posts

Uber Geek

Trusted

#454916 3-Apr-2011 21:43

Numbers are handy, so im making use of chromes benchmarking feature to prove a point here.
http://www.chromium.org/chrome-benchmarking-extension
time to first paint is what i'm interested in, which is the time it takes before it begins loading the first item on the page. Of course total page load time is handy too.

So far after three iterations of loading the "New Zealand" wikipedia article im looking at a first paint time of 33063.0 (33 seconds), with a total document loadmean of 362194.0 (362 seconds), this is for every item on the page to be loaded. The first few seconds after the first paint, all text and most images have been loaded, it just sits there waiting for 'upload.wikimedia.org' for a while.

For a comparison Geekzone.co.nz's mean paint time after 3 iterations is 690.0ms to the first item, then after 720.5ms the entire site is loaded (impressive btw, thats literally faster than the blink of an eye once it begins loading (200-400ms

)

So far my list of sites is
wikipedia.org
vodafone.co.nz
nzcouriers.co.nz
godaddy.com
microsoft.com
facebook.com
guardian.co.uk
adobe.com
arstechnica.com
nytimes.com
typekit.com

booleanvalue

27 posts

Geek

#455009 4-Apr-2011 09:42

Pretty interesting stats there eXDee

Keep up the good work, be very interesting to see what comes of all of this..

Ragnor

8196 posts

Uber Geek

Trusted

#455073 4-Apr-2011 12:29

Haven't seen any issue with any of those sites at home on Telecom ADSL.

Checked with Firefox's firebug net panel and httpfox, didn't see any unusual latency or delay on any of the http requests.

Might be specific to a particular region in NZ, those going via a certain regional gateway etc?

Ragnor

8196 posts

Uber Geek

Trusted

#455076 4-Apr-2011 12:31

eXDee: Does anyone know if theres a better way to do it than the helpdesk? I don't want it to just be dismissed as a generic speed complaint which i know they get a lot of due to peoples bad lines etc.

Logged it here in case it helps.
http://www.geekzone.co.nz/fault.asp

In my experience they have pretty good turn around on requests/issues submitted via their online contact us form at:
http://telecom.custhelp.com/app/ask

It seems to bypass the L1 script reading phone answerers.

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | ... | 10