As we’ve previously reported, a variety of factors can cause Safari for Mac OS X to slowly load pages, open new tabs and windows, and perform other operations.
Apple has now posted a knowledge base article titled “Safari 5.0.1 or later: Slow or partial webpage loading, or webpage cannot be found,” which lists two potential fixes for the issue.
The first echoes our previously posted fix for the issue, switching DNS servers from those generated by your ISP to those offered by OpenDNS. To do so:
Open System Preferences and click “Network”
Select your connection method (AirPort, Ethernet, etc.)
Enter the following items in the “DNS Server” field: 208.67.222.222, 208.67.220.220
Click Apply
Or you can try Google’s public DNS servers: 8.8.8.8 and 8.8.4.4.
Apple’s second fix involves disabling DNS prefetching. We previously noted that anecdotal evidence suggests that this issue is caused by a problem with Safari 5.0′s DNS prefetching mechanism, which appears to send more requests than allowed by some ISPs. This issue may also cause problems with some routers.
Apple’s instructions for disabling prefetching in Mac OS X require opening the Terminal (click the Spotlight icon–magnifying glass–in the upper-right portion of the screen and type “Terminal”) then entering the following command:
Apple also recommends upgrading router firmware or switching routers, and offers instructions for re-enabling DNS prefetching if a firmware update or router switch resolves the issue.
For full instructions, including prefetching disabling instructions for Windows, and re-enabling prefetching, see the knowledge base article.
Obsessed with tech since the early arrival of A/UX on Apple, Sudz (SK) is responsible for the original editorial direction of AppleToolBox. He is based out of Los Angeles, CA.
Sudz specializes in covering all things macOS, having reviewed dozens of OS X and macOS developments over the years.
In a former life, Sudz worked helping Fortune 100 companies with their technology and business transformation aspirations.
You state “Apple’s instructions for disabling prefetching in Mac OS X require opening the Terminal (click the Spotlight icon–magnifying glass–in the upper-right portion of the screen and type “Terminal”) ” Sorry but I cannot determine how in the heck to do this on my wife’s iPad Mini. On one screen I do see the magnifying glass and when I enter Terminal the results are all webpages.
I can’t fathom why Apple wouldn’t have it monitor itself, and if the prefetching slows down responses or get blocked, dial itself down or turn prefetching off.
Guys, even if changing DNSs and disabling prefetching fixed it for you, please submit bug reports to Apple through feedback assistant, this should all work out of the box and enough of us have to comment for them to notice.
Seems this problem is more pervasive than just some old routers. Was constantly having problems with Safari stalling during page loads. Debugging network, DNS, routers, wasting a considerable amount of time and finally found this fix. I use T-Mobile hotspots, AT&T hotspots, corporate intranets, none of which can be fixed by “buy a new router”. Applied the tip here and BAM, life is good.
This is a Safari defect, not a feature. Very disruptive and distracting. Raises cost of ownership of Mac for most users and most users cannot be expected to use arcane methods like Terminal commands to fix Apple’s defective features.
This is the solution for me (“Enter the following items in the “DNS Server” field: 208.67.222.222, 208.67.220.220). I had to disable dhcp to be able to change the dns entry. Thanks god the new dns-entries remained as I switched dhcp on again.
I am using a G5 with OSX 10.5.8 and Safari 5.0.6 and a dLink router. The combination of the three became superslow since a while. Now everything is okay again, feels a bit like a new Mac :o) .
U generated a number of terrific tips in your post, _Fix Safari Slow, Stalled Page Loads by Disabling DNS Prefetching – Apple Toolbox_.
I will be coming back again to ur page in the near future.
Thanks -Jimmie
This worked for me, so far touch wood. Couldn’t believe that a brand new 2.7ghz, 768gb, 16gb Macbook Pro Retina was so slow using Safari. Hanging all the time on most things Google related. Unbelievable. Fingers crossed the fix is permanent.
Seems to work for my desktop, which as of a few weeks ago suddenly started loading super slow -and I mean SUPER slow. I don’t remember updating, but at least this helps. Thanks!
Since the Macbook has been used with several different ISP’s and routers, I decided that the DNS is probably not be the problem and went straight to fix 2 (Disabling the prefetching). It’s loading everything much quicker than before! Some sites are still slow, but I’m pretty sure that it’s the site’sserver and no longer the Macbook.
The first solution worked great for me! Safari was all of a sudden slow after a rainy night in LA (the rain usually messes with our internet speed) and never returned to normal after that. Thanks!
This worked like a charm. Funny thing is I am already using opendns, and my ‘outdated non-robust’ router as described in the apple document is a apple airport extreme dual band on the latest firmware…
I just tried this, and it’s amazing. A lot of my webpages wouldn’t load the comment sections, like http://www.CBC.ca, and I would have to reload the page a couple of times. It seems to be working exceptionally well.
You state “Apple’s instructions for disabling prefetching in Mac OS X require opening the Terminal (click the Spotlight icon–magnifying glass–in the upper-right portion of the screen and type “Terminal”) ” Sorry but I cannot determine how in the heck to do this on my wife’s iPad Mini. On one screen I do see the magnifying glass and when I enter Terminal the results are all webpages.
I can’t fathom why Apple wouldn’t have it monitor itself, and if the prefetching slows down responses or get blocked, dial itself down or turn prefetching off.
Guys, even if changing DNSs and disabling prefetching fixed it for you, please submit bug reports to Apple through feedback assistant, this should all work out of the box and enough of us have to comment for them to notice.
Seems this problem is more pervasive than just some old routers. Was constantly having problems with Safari stalling during page loads. Debugging network, DNS, routers, wasting a considerable amount of time and finally found this fix. I use T-Mobile hotspots, AT&T hotspots, corporate intranets, none of which can be fixed by “buy a new router”. Applied the tip here and BAM, life is good.
This is a Safari defect, not a feature. Very disruptive and distracting. Raises cost of ownership of Mac for most users and most users cannot be expected to use arcane methods like Terminal commands to fix Apple’s defective features.
Thanks for the fix!
Fix of 208.67.220.220 and 208.67.220.220 still works.
Running 10.11.2 El Capitan, and Safari 9.0.2
Still not sure why the usual DNS would “all of a sudden” (last month or so) mess up…but….
THANKS!
This is the solution for me (“Enter the following items in the “DNS Server” field: 208.67.222.222, 208.67.220.220). I had to disable dhcp to be able to change the dns entry. Thanks god the new dns-entries remained as I switched dhcp on again.
I am using a G5 with OSX 10.5.8 and Safari 5.0.6 and a dLink router. The combination of the three became superslow since a while. Now everything is okay again, feels a bit like a new Mac :o) .
You made my day, thanks again!
Andi
U generated a number of terrific tips in your post, _Fix Safari Slow, Stalled Page Loads by Disabling DNS Prefetching – Apple Toolbox_.
I will be coming back again to ur page in the near future.
Thanks -Jimmie
This worked for me, so far touch wood. Couldn’t believe that a brand new 2.7ghz, 768gb, 16gb Macbook Pro Retina was so slow using Safari. Hanging all the time on most things Google related. Unbelievable. Fingers crossed the fix is permanent.
Excellent! solved my problem.
Seems to work for my desktop, which as of a few weeks ago suddenly started loading super slow -and I mean SUPER slow. I don’t remember updating, but at least this helps. Thanks!
Since the Macbook has been used with several different ISP’s and routers, I decided that the DNS is probably not be the problem and went straight to fix 2 (Disabling the prefetching). It’s loading everything much quicker than before! Some sites are still slow, but I’m pretty sure that it’s the site’sserver and no longer the Macbook.
Thanks!
Eugene
Wow What a difference
208.67.220.220
208.67.220.220
Worked wonderfully !
Do I delete the other DNS in prefs? Or just leave the long list?
Worked like a charm. Thankyou
I tried using the Google DNS servers and it is working great!! FINALLY!!
The first solution worked great for me! Safari was all of a sudden slow after a rainy night in LA (the rain usually messes with our internet speed) and never returned to normal after that. Thanks!
This worked like a charm. Funny thing is I am already using opendns, and my ‘outdated non-robust’ router as described in the apple document is a apple airport extreme dual band on the latest firmware…
seems to help with my netgear router… faster now when using safari 5 with less stalls
I just tried this, and it’s amazing. A lot of my webpages wouldn’t load the comment sections, like http://www.CBC.ca, and I would have to reload the page a couple of times. It seems to be working exceptionally well.