Currently Being ModeratedJun 17, 2013 9:48 AM (in response to bug00)
1. Under the Safari menu, select 'Reset Safari'. You may not want to reset everything, such as 'saved names and passwords'.
2. Delete the Safai .plist.
Quit the application.
You need to look in your user Library/Preferences for the .plist. Hold down the option key while using the Finder “Go To Folder” command. Enter ~/Library/Preferences/com.apple.Safari.plist. Move the .plist to your desktop.
Open the application and test. If it works okay, delete the plist(s) from the desktop.
If the application is the same, return the .plist(s) to where you got them from, overwriting the newer ones.
If you prefer to make your user library permanently visible, use the Terminal command found below.
You might want to bookmark the command. I had to use it again after I installed 10.8.4. I have also been informed that if you drag the user library to Finder it will remain visible.
If that works with Safari, try the same steps for Firefox and Chrome.
Currently Being ModeratedJun 17, 2013 10:52 AM (in response to Eric Root)
Thanks for taking a stab at it, Eric. I tried both suggestions in Safari, and unfortunately neither the reset nor removing the .plist had any effect on the load times of those two particular sites. I didn't try it in the other two affected browsers because the procedure showed no impact in Safari (and as resetting does cause some additional effort in future browsing).
I do thank you for the idea.
Currently Being ModeratedJun 17, 2013 10:59 AM (in response to bug00)
Have you tried to change the DNS server in > System Prefference > Network > "Network adapter" > Advance > DNS > and add google´s DNS servers?
Google´s Public DNS
Currently Being ModeratedJun 17, 2013 1:06 PM (in response to bug00)
Please post a link to one of the pages in question.
Currently Being ModeratedJun 17, 2013 1:29 PM (in response to zpnwr)
Thanks for pitching in, Kristoffer. I hadn't tried Google's public DNS, but as I mentioned I had tried OpenDNS's, which provided no faster load time on those sites. At your behest, though, I did try Google's DNS servers, and unfortunately, they didn't change the load time either. Again, thanks for the idea.
Currently Being ModeratedJun 17, 2013 1:37 PM (in response to Linc Davis)
Linc, thanks for taking a look at it. One of the sites in question is http://www.TroubleEnsued.com
Again, the strange thing about this situation is that two same-model computers running side by side on the same wireless network using the same DNS servers are loading this site with consistantly different speeds. So to a certain degree no matter what speed it loads for others outside my network...I will still need to figure out why it loads so radically differently on our two laptops here.
Only difference I can see so far is that the slower one is running OS 10.8.4, the faster one is still on 10.8.3. However, as I mentioned, all of the rest of my urls are resolving as quickly as usual so doesn't seem to be a systemic issue. That's what makes it a mystery.
Currently Being ModeratedJun 17, 2013 11:06 PM (in response to bug00)
time curl -I http://www.troubleensued.com
Currently Being ModeratedJun 18, 2013 2:01 PM (in response to Linc Davis)
Thank you very much for taking an interest in this mystery, Linc. I followed the procedure you detailed.
The first time I did it, it didn't return any output within five seconds. But as I was rereading your note to make sure I did it correctly before quitting Terminal, it eventually did return this as the first of those three lines:
I also tried the same procedure in Terminal on my husband's MBP which I mentioned consistently loads this same page quickly. (As detailed before, his is MBP the same model machine, on the same wireless network, with the most obvious difference I can think of being that he is running OS 10.8.3 and I am running OS 10.8.4). The first of those three lines in Terminal on his machine was:
I guess comparison of this data backs up my contention that his MBP does load this page faster.
By the way, just for comparison, I also tried the same Terminal procedure on my MBP with another unrelated website (Facebook). It returned this output immediately, and shows that my connection does perform well with other sites.
Currently Being ModeratedJun 18, 2013 2:17 PM (in response to bug00)
That means the problem is not caused by your browser. It's a network or system issue. The network is apparently ruled out by your results.
Currently Being ModeratedJun 18, 2013 3:49 PM (in response to Linc Davis)
Thanks for further inspection, Linc. Followed your instructions. Disconnected all peripherals. Booted in safe mode.
Terminal output after a wait was:
For comparison, while booted in safe mode, I also again tried running that terminal command directed to the Facebook website. Output once again was almost immediate, a considerably faster:
As instructed, I rebooted as usual (not in safe mode), and Terminal output was:
Tried again with peripherals reconnected, and it was:
Currently Being ModeratedJun 18, 2013 4:20 PM (in response to bug00)
What do you get with other sites, such as this:
time curl -I http://www.apple.com
Currently Being ModeratedJun 18, 2013 4:54 PM (in response to Linc Davis)
Much faster, as I mentioned on both previous test posts when I tried it the command directed to Facebook.com. I tried the one you just provided to Apple, terminal returned:
So...it's fast! The slowdown *only* seems to occur with two sites that I know are hosted on the same GoDaddy server. But I eliminated my initial concept that it was a server problem because as previously stated (and documented today through Terminal), my husband's MBP does not experience this slowdown to either site at all! Thanks for pondering this, Linc. Strangest thing, huh?
Currently Being ModeratedJun 18, 2013 5:19 PM (in response to Linc Davis)
Linc...I may be onto something. I need to go offline now, so let me experiment with it more overnight before I jump to a conclusion. If this turns out to be the solution, I'll post in the AM. Again, thank you so much for working with me on this. I won't leave you hanging...