What on earth is going on with these loading times?!?

Toggle sidebar Toggle sidebar
J

jbkly

Honorable
Nov 9, 2013
14
0
10,510
I am having insane page loading times trying to load certain certain scripts and elements in common sites like google.com and facebook.com. See this screenshot:

nliIMWd.png


As you can see from the Chrome developer tools, the browser spent 2.3 minutes waiting to receive Google's 13.5KB logo image before failing to load it. Another Javascript call took 27 seconds.

This is happening intermittently but constantly on various sites, in all browsers. Sometimes I can't reach any Google site, other times it's fine. While this is happening, my internet connection as measured by SpeedTest.net is still solid:

3119459895.png


Any ideas what's going on, or how to troubleshoot it?
 
Sort by date Sort by votes
J

jbkly

Honorable
Nov 9, 2013
14
0
10,510


Thanks for the suggestion. How should I use the site you linked? I'm assuming you mean I should run a tracert command from my computer to the site I'm trying to reach, in this case google.com. I've done that while the site is trying to load, and the results don't seem to tell me anything:

C:\Users\jbkly>tracert google.com

Tracing route to google.com [173.194.33.134]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 11 ms 7 ms 96.184.230.1
3 13 ms 11 ms 13 ms te-0-2-0-15-ur07.seattle.wa.seattle.comcast.net
[68.85.240.129]
4 9 ms 16 ms 10 ms ae-20-0-ar03.burien.wa.seattle.comcast.net [69.1
39.164.125]
5 11 ms 10 ms 9 ms ae-20-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.129]
6 14 ms 14 ms 10 ms he-1-4-0-0-11-cr01.seattle.wa.ibone.comcast.net
[68.86.95.213]
7 12 ms 11 ms 13 ms be-12-pe03.seattle.wa.ibone.comcast.net [68.86.8
4.106]
8 19 ms 20 ms 17 ms 75.149.231.90
9 11 ms 12 ms 15 ms 209.85.249.32
10 17 ms 18 ms 16 ms 209.85.244.61
11 13 ms 11 ms 19 ms sea09s17-in-f6.1e100.net [173.194.33.134]

Trace complete.
 
Upvote 0 Downvote
J

jbkly

Honorable
Nov 9, 2013
14
0
10,510


It's random files. This screenshot of Chrome dev tools when I tried to load Facebook.com shows that it took 12 seconds to load the Facebook html file and then up to 56 seconds to get various other random things. Some things are still waiting to load right now, over 6 minutes later.

CUuQx33.png


But if it was an ISP issue, wouldn't it affect all my other devices? This only affects my PC, not my macbook, android smartphone/tablet, wife's iphone, chromecast, or smart TV.

If it's an issue with my PC's network connection (motherboard, network adapter, router, etc), why does it not affect certain sites and my upload/download speeds stay consistently great?

I appreciate your help, I'm just so stumped.



Thanks for the suggestion. I have in fact used Namebench and a couple other tools, and I've tried changing my DNS servers several times, both locally on my PC and at my router. I'm currently using a regional DNS server that tested fastest on DNS Benchmark and Google's own DNS (8.8.8.8) as my secondary.

Here's more info from a previous post I posted (that no one responded to), including all the other things I've tried:

I have a relatively fast Comcast connection (averaging 60Mbps/10Mbps/10ms ping) through my Trendnet 802.11ac router and Edimax USB adapter. However, multiple times per day I get this intermittent issue where certain websites become inaccessible or extremely slow. They are high-profile sites like Google (including Gmail, Google Maps, and other Google services), Facebook, Bank of America, Twitter, and others. When this happens, the sites don't give any sort of error message, but they simply endlessly sit there loading while the browser status bar reads, "Waiting for google.com" or "Waiting for fbexternal-a.akamaihd.net" or the like. This will go on for minutes or long periods of time, and what is crazy is that when this happens, other sites (such as Bing.com and Speedtest.net) are completely fine and load quickly as they should. I spend most of my workdays at the computer and find myself regularly having to switch over to search with Bing because Google search has slowed to a crawl. When these issues happen, a quick check of www.downforeveryoneorjustme.com shows that the sites are fine, Speedtest.net shows that my internet connection is fine, and my download speeds are top-notch.

I normally use Google Chrome, but the issue applies the same whether I use Firefox, IE11, or Opera. However, it doesn't seem to be my router, because when the issue is occurring my Android smartphone, on the same wireless network, can access the sites just fine.

Here are the things I've tried already, to no avail:
- clearing all user data in my browser
- uninstalling/reinstalling Google Chrome browser
- switching from Chrome beta to stable channel
- removing all Chrome extensions
(the preceding steps were all before I deduced that the issue is cross-browser)

- ipconfig /flushdns
- switching DNS servers to Google DNS, OpenDNS, and finally local DNS servers (on both PC and in router admin)
- disabled teredo tunneling interface (this broke something so I had to re-enable it)
- deleting Windows hosts file
- running antivirus & malware scans
- resetting cable modem
- resetting router
- disabling/re-enabling wireless network adapter
- I've even tried running tracert when the issue is happening, and the response times to google.com seem normal. Yet I could not get any browser to connect to google.com.
- purchased a new router from a different manufacturer

So the issue is not browser-specific, and it occurs only my desktop PC and no other devices (Macbook, Android smartphone, tablet, wife's iPhone, all connected to the same wireless access point).

What on earth am I missing?? Any ideas?

My setup:
Windows 7 Professional 64-bit Service Pack 1
Intel Core i5-2500 3.3Ghz quad-core CPU
16GB RAM
Two SSD drives
Edimax AC1200 Wireless USB Adapter (dual band 802.11ac)
ASUS RT-AC66U dual band AC1750 router (previously a Trendnet AC1750 router)
 
Upvote 0 Downvote
A

azm-mjza

Honorable
Nov 24, 2013
5
0
10,510
hello
you might want to check you your services that are connecting to the internet via net stat.
if you do self-maintenance on your pc you should now what services are being used, if not try learning what services does.
you might also want to consider what software you have installed that is relative to the date when your connection started to stutter.
better to be safe than sorry, scan for unwanted elements with an antimalaware to see if there is something fishy going in the background. popular sites like facebook and google may seem a possible gateway that triggers a hidden agenda on your pc.

if you want to really confirm that it is only your pc qos limit bandwidth from your other devices to your wifi adapter and mac filter you pc for unlimited bandwidth and see if the problem persists. if it does, i would also suggest uninstalling browsers, delete cookies, temp files, history, downloads, and do a fresh install.

from my experience it seems quite unlikely that it is your networking (modem, router, cable, wifi signal) than can cause delay in accessing webpages.
 
Upvote 0 Downvote
J

jbkly

Honorable
Nov 9, 2013
14
0
10,510


I have run malware and rootkit scans with 3-4 different antivirus programs, but I haven't tried netstat or QoS limiting yet. I will try those approaches and report back. Thanks for the suggestions.
 
Upvote 0 Downvote
J

jbkly

Honorable
Nov 9, 2013
14
0
10,510


I ran "netstat -b" while the connection was acting up just now. I had Dropbox, Steam, and Chrome browser running with only one tab open. Is it normal to see 67 connections for one instance of the browser? It also took around 3 minutes for netstat to finish listing out these connections:

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:2559 jbkly-desktop:54580 TIME_WAIT
TCP 127.0.0.1:19872 jbkly-desktop:49248 ESTABLISHED
[Dropbox.exe]
TCP 127.0.0.1:49248 jbkly-desktop:19872 ESTABLISHED
[Dropbox.exe]
TCP 192.168.1.50:49269 snt-re2-9c:http ESTABLISHED
[Dropbox.exe]
TCP 192.168.1.50:54372 a23-59-190-115:http TIME_WAIT
TCP 192.168.1.50:54373 a23-59-190-115:http TIME_WAIT
TCP 192.168.1.50:54374 a23-59-190-115:http TIME_WAIT
TCP 192.168.1.50:54375 a23-59-190-115:http TIME_WAIT
TCP 192.168.1.50:54376 a23-59-190-115:http TIME_WAIT
TCP 192.168.1.50:54377 a23-59-190-115:http TIME_WAIT
TCP 192.168.1.50:54379 a23-59-190-105:http TIME_WAIT
TCP 192.168.1.50:54380 a23-59-190-105:http TIME_WAIT
TCP 192.168.1.50:54381 a23-59-190-105:http TIME_WAIT
TCP 192.168.1.50:54382 a23-59-190-105:http TIME_WAIT
TCP 192.168.1.50:54383 a23-59-190-105:http TIME_WAIT
TCP 192.168.1.50:54391 a23-59-190-105:http ESTABLISHED
[steam.exe]
TCP 192.168.1.50:54393 69.22.148.136:http TIME_WAIT
TCP 192.168.1.50:54408 74.125.20.84:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54410 sea09s18-in-f3:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54411 pd-in-f95:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54413 sea09s18-in-f18:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54414 pd-in-f95:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54415 ie-in-f125:5222 ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54416 sea09s15-in-f9:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54417 sea09s16-in-f1:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54421 sea09s02-in-f8:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54422 sea09s18-in-f3:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54423 sea09s17-in-f14:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54424 do-19:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54425 192.168.1.245:8008 ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54435 pc-in-f193:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54456 a23-59-191-49:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54458 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54459 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54462 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54464 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54465 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54466 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54467 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54468 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54469 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54472 sea09s18-in-f25:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54473 sea09s15-in-f15:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54475 sea09s17-in-f5:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54478 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54479 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54483 a23-59-191-49:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54484 a23-59-191-49:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54485 a23-59-191-49:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54489 165.254.47.136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54492 sea09s02-in-f4:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54493 a23-59-191-35:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54496 165.254.47.136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54499 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54500 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54503 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54504 165.254.47.128:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54506 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54507 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54509 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54512 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54513 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54514 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54515 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54516 a23-59-189-233:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54517 a23-59-189-233:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54523 sea09s16-in-f0:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54524 a23-198-164-136:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54527 ec2-54-243-202-159:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54532 a23-59-189-120:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54537 165.254.96.142:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54538 165.254.96.142:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54540 2.19.129.169:http CLOSE_WAIT
[chrome.exe]
TCP 192.168.1.50:54541 165.254.96.142:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54544 phx1-dw-cbsimg-xw-lb:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54548 phx1-dw-cbsi-xw-lb:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54549 phx1-dw-cbsi-xw-lb:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54552 phx2-aud-apex-ws-lb:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54553 2.19.143.139:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54565 50.31.164.192:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54581 sea09s17-in-f3:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54589 sea09s01-in-f11:https ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54590 sea09s01-in-f20:http ESTABLISHED
[chrome.exe]
TCP 192.168.1.50:54591 sea09s01-in-f20:http ESTABLISHED
[chrome.exe]
 
Upvote 0 Downvote
A

azm-mjza

Honorable
Nov 24, 2013
5
0
10,510
hey
i forgot to mention, when you start up your computer verify what process (ctrl alt delete ) are on, repeat this again a a later point after some use when everything is stable, and immediately do this when you feel the Internet lag or stutter.

if your net stats only show dropbox and chrome it seems tricky. since you claim the problem persists with all browsers. i dont use dropbox but if google services and/or facebook services are being used to log in to dropbox your net stats indicate dropbox is trying to connect to different ips, im no expert but thats what im inferring.

if its not virus malaware situation, have you tired deleting google/facebook files in>>

C:/Windows/System32/Drivers/etc

i would also suggest setting your ip4 address, but even so it seems strange that google just hangs up only on your pc.

might i suggest that if you have gone to the extent of purchasing a new router why not reformat your pc and re install windows again. seems tedious but its about a 2 hour operation. given the fact that if you wait 3 minutes to wait for google to load, after 60 waiting sessions .....

 
Upvote 0 Downvote
J

jbkly

Honorable
Nov 9, 2013
14
0
10,510


I think I've narrowed it down to my wireless adapter, an Edimax AC1200 USB 3.0 adapter. My computer having the issue is on the opposite end of the house from my router and modem, so I had to bite the bullet and buy a 100-ft ethernet cable and snake it through the house to connect directly to my router, but that seems to eliminate the issue. I was surprised, since I have no other indication of problems with the wireless network on any other devices in the home, and I consistently got such great Speedtest results through that adapter, but I guess I should have tried this sooner.

Looking at the Edimax AC1200 wireless adapter on Newegg, I found that some other reviewers experienced similar issues with pages loading forever and images failing to load on web pages. So it looks like something to do with either the Edimax adapter itself or the USB drivers.

Are you using a wireless adapter or connecting directly to your router?
 
Upvote 0 Downvote
O

oxford0614

Honorable
Dec 12, 2013
2
0
10,510
Hey, apparently it is our modem. We do use a wireless adapter but I tried plugging directly into the modem and it made no difference. I took my laptop over to my daughter's house and got on her network and everything worked great. Called my ISP back, they ran a test on the modem and said it "came back with errors." It would have been nice if they'd done that before.
Glad you were able to solve your problem by running cable, is there a way to boost your wireless?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom