Long load time for websites, seems to take a long time with TLS handshake

[jnelsoninjax]

Last week we had an issue with Comcast and slow upload speed. They diagnosed the issue to be at a node and fixed it, but since that point whenever I visit any website, it seems to take longer then normal times to load, it seems to be taking along time with the TLS handshake. Could this be an issue with the ISP or is it more of a local issue? The modem is brand new and according to Comcast our lines are fine. The speedtest shows really good as well: http://speedtest.xfinity.com/results/JJYLX02B52KAH3P 180 Down 12 Up. Any help would be appreciated!

[strotee]

Experiment with changing the DNS to 1.1.1.1 (CloudFlare) or Google (8.8.8.8). 

[jnelsoninjax]

20 minutes ago, ozzy76 said:

Experiment with changing the DNS to 1.1.1.1 (CloudFlare) or Google (8.8.8.8). 

Actually have the router set to 1.1.1.1 and 8.8.8.8 as secondary I also have done a ipconfig/flushdns as well as a test.

[+BudMan MVC]

51 minutes ago, jnelsoninjax said:

it seems to take longer then normal times to load

And what does that mean exactly.. 4 seconds when they use to load in 2.. 30 seconds when they use to load in 20?

 

What browser are you using?  Firefox has built in tools to show you exactly how long a website takes to load, etc..

 

 

If you think its dns.. That should show up or can be tested with simple query from cmdline be it nslookup, dig, host, etc.  This "seems" to take longer is impossible to troubleshoot..

 

Are you running through a VPN... What sort of test did you do on your dns?

[jnelsoninjax]

19 hours ago, BudMan said:

And what does that mean exactly.. 4 seconds when they use to load in 2.. 30 seconds when they use to load in 20?

 

What browser are you using?  Firefox has built in tools to show you exactly how long a website takes to load, etc..

 

If you think its dns.. That should show up or can be tested with simple query from cmdline be it nslookup, dig, host, etc.  This "seems" to take longer is impossible to troubleshoot..

 

Are you running through a VPN... What sort of test did you do on your dns?

I am using firefox, and sites such as Neowin load in ~3 seconds, whereas gmail takes 2.26 mins to fully load. Running a tracert to mail.google.com shows all requests timing out. I really notice the long load time using Thunderbird to retrieve my email, which is what prompted me to do a tracert to gmail. So what do make from this? I am not using a VPN, and have not done any testing on the DNS server, I was simply responding to the suggestion to switch DNS servers.

[+BudMan MVC]

What is taking so long in the load of gmail?

 

So from work - with a proxy being all the way in hou while im in chicago gmail takes

 

91 requests
7.81 MB / 0 GB transferred
Finish: 17.97 s
DOMContentLoaded: 1.62 s
load: 4.01 s

 

So your going to have to look to see what is taking so long in the process.  Your saying the website takes that long in thunderbird?  What are you thunderbird settings.. As to traceroute to what exactly? what fqdn are you tracing too - there is a difference between using the web interface and thunderbird to pull your mail, are you using imap, pop? Do other traceroutes fail all the way or just some hops?  Let me know the fqdn your running the trace too and I can take a look to see if it answers.  Not all hops or end IPs will answer a trace.

 

Here is trace from home network to web interface address.

 

Its quite possible there is a problem between your path to where your going to get your mail... Possible packet loss along the way, etc.. Try doing a mtr trace to it

 

Notice no loss on any of the hops.

C:\>tracert -d mail.google.com

Tracing route to googlemail.l.google.com [172.217.1.37]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.9.253
  2    12 ms     8 ms     9 ms  50.4.132.1
  3     9 ms    15 ms    12 ms  76.73.171.77
  4    11 ms    11 ms    11 ms  76.73.164.141
  5    10 ms    16 ms    13 ms  76.73.164.121
  6     9 ms    18 ms    11 ms  76.73.164.109
  7    12 ms    13 ms    17 ms  76.73.164.105
  8    19 ms    12 ms    17 ms  76.73.164.65
  9    11 ms    10 ms    20 ms  76.73.191.224
 10    11 ms    20 ms    11 ms  75.76.35.8
 11    19 ms    18 ms    14 ms  72.14.211.145
 12    12 ms    11 ms    12 ms  108.170.244.1
 13    14 ms    14 ms    24 ms  216.239.41.161
 14    19 ms    14 ms    11 ms  172.217.1.37

Trace complete.

[jnelsoninjax]

OK, @BudMan I am using imap to access my gmail. I ran MTR, here are the results:

 

Quote

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            Linksys12611 -    0 |   44 |   44 |    0 |    0 |    0 |    0 |
|                           96.120.21.205 -    3 |   40 |   39 |    0 |   12 |   28 |   11 |
|ge-3-1-ur01.normandy.fl.jacksvil.comcast.net -    0 |   44 |   44 |    8 |    9 |   16 |   15 |
|                            68.87.167.93 -    3 |   40 |   39 |    0 |   12 |   30 |   12 |
|be-33489-cr02.miami.fl.ibone.comcast.net -    3 |   40 |   39 |    0 |   20 |   31 |   22 |
| be-12297-pe03.nota.fl.ibone.comcast.net -    3 |   40 |   39 |    0 |   22 |   37 |   20 |
|                           23.30.207.242 -    3 |   40 |   39 |    0 |   20 |   36 |   17 |
|                          108.170.249.17 -    3 |   40 |   39 |    0 |   21 |   37 |   20 |
|                           66.249.95.215 -    3 |   40 |   39 |    0 |   21 |   37 |   19 |
|                mia07s34-in-f5.1e100.net -    0 |   44 |   44 |   16 |   19 |   27 |   27 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

  So if I read this correctly, there is packet loss on some of the servers, are these Comcast's servers or what are they?

[+BudMan MVC]

yeah you have packet loss to some hops.  what is the fqdn your hitting?

 

That first hop is your router, the 2nd hop is to your isp.. Since you have packet loss there this is most likely where the problem is..  Then the rest of the hops are your path from your isp to get where your going. 

 

I would suggest you you run some high number of pings to say that 2nd hop IP and see what you get for response.. Say ping 1000 times what do you show for packet loss?