17
9
For some reason Google Chrome is slow when I'm working against localhost. I had the same problem in Firefox 3.5 but I changed some IPv6 setting in about:config
which fixed the issue. I think the same problem occurs in Google Chrome, but I can't find out how to fix it.
Any ideas?
6This makes a huge difference. Both lines were commented out for me in Windows 7, so I uncommented the IPv4 line and everything works great now. – Ben Mills – 2010-02-01T16:27:01.063
After trying loads of different things, @RustyX gave me the best answer. If I turn off the Wi-Fi and just use the ethernet connection, it works sooo fast. Thanks dude. – ingh.am – 2017-03-08T15:13:26.290
2I've been using this fix up until Chrome 8, but now that Chrome 9 has been released, it seems to be slow again. Has anyone found a fix for the current version? – Douglas – 2011-02-21T10:45:13.253
@Pascal: Thank you so much. This issue as been annoying me forever. – Tomalak – 2011-09-13T16:12:03.573
You're welcome :-) Was just a wild guess, but nice to seen it worked ! (might be useful one day on another, actually ! ) – Pascal MARTIN – 2009-09-19T15:56:07.247
@blahblah - You should mark Pascal's answer as "accepted". @Pascal - thanks so much for this fix, this was really slowing me down as I was testing sites locally in Chrome. – Herb Caudill – 2009-09-28T12:49:56.943
2Can someone explain why does this work? – Pacerier – 2012-07-16T17:01:12.113
http://crazyviraj.blogspot.com/2009/09/fix-for-slow-firefoxchrome-connects-to.html – psychotik – 2009-10-29T09:56:09.100
Doesn't solve the issue for me. – ysrb – 2013-10-24T14:01:37.483
Doesn't work for me (Win7 x64). As soon as wi-fi is on, accessing localhost is slow, when I disable wi-fi then it's fast. Tested in IE, FF and Chrome. NB I do not use any web filtering. – rustyx – 2014-05-17T18:28:52.193