I hope someone will be able to help this n00b with his problem. I've noticed this started happening after the latest 378.53 firmware, and I did not have this problem before. Not sure if it's directly connected to the new firmware, but it's my observation and it won't hurt to ask.
Lately I've noticed it takes good 3-6 seconds for my Chrome (even Firefox) to open simple Google search page. I don't use any proxies. The only thing that's different is, I started blocking one URL in my router (don't want my kid to play that game, it has some very bad, not very healthy reviews). I tried network tools / PING and this is my result now:
Before my ping was 24 - 40 ms, but this is unusually high now...
I'd appreciate any input guys. Thanks in advance!
@SmallNetGuy
Maybe traceroute can help you see what takes time.
For Windows run tracert
www.google.com,
for Mac OS X/GNU Linux run traceroute
www.google.com.
It will give you something like this:
#traceroute
www.google.com
traceroute to
www.google.com (216.58.209.132), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.1) 3.099 ms 2.265 ms 2.185 ms
2 c213-200-154-13.bredband.comhem.se (213.200.154.13) 3.392 ms 3.746 ms 3.491 ms
3 213.200.165.169 (213.200.165.169) 16.452 ms
213.200.165.171 (213.200.165.171) 15.065 ms 14.934 ms
4 213.200.163.97 (213.200.163.97) 21.353 ms 21.184 ms 21.013 ms
5 mtc-core-1-be6.net.comhem.se (213.200.162.65) 15.377 ms
nap-core-1-be7.net.comhem.se (213.200.162.67) 20.823 ms
nap-core-1-be6.net.comhem.se (213.200.162.63) 19.902 ms
6 216.239.49.217 (216.239.49.217) 19.557 ms 15.113 ms 18.188 ms
7 arn09s05-in-f4.1e100.net (216.58.209.132) 22.489 ms 20.458 ms
216.239.40.178 (216.239.40.178) 43.429 ms