Safari issues (pages not loading, slow)

London Geezer

Legend
Supporter
Hello guys,

I have an issue that's driving me bonkers. I'm on a new Macbook Pro, Yosemite, and Safari is a bloody nightmare lately. It often won't load some pages (B3D being one of them, but also other random pages at any random time), or be extremely slow (progress bar getting to about half then stopping), while Chrome would be perfectly fine at the same time for the same exact pages.

Saving the 'Just use Chrome' comments for later, has anyone had the same problem? And fixed it, somehow?

It is literally killing my mood and no matter how much I search on Google, I can't find a real solution.

Help!
 
does safari have the ability to "inspect" the traffic and process? in Chrome you can inspect and see what taking the longest time.
 
I've been been having general slowness issues in Safari (MBP, Yosemite) recently, maybe for the past week or 10 days, here and on other forums. I think I'm seeing the same in FF, but it's hard to tell. I've been getting some whacky results from speedtest.net too, eg. pings in the 100's of ms. As of yet I'm not sure whether to point my finger of blame at the browser, the web-sites in question, my ISP, my MBP hardware or software, or my own incompetence.
 
Well when one page won't load at all for a while on Safari, while it does instantly on Chrome, then I'd think it's a Safari problem. Just can't find a solution online for the life of me.
 
can you right click the page and look for debugging option? on CHrome it was Inspect element. Dunno safari have or not.
 
I've been been having general slowness issues in Safari (MBP, Yosemite) recently, maybe for the past week or 10 days, here and on other forums. I think I'm seeing the same in FF, but it's hard to tell. I've been getting some whacky results from speedtest.net too, eg. pings in the 100's of ms. As of yet I'm not sure whether to point my finger of blame at the browser, the web-sites in question, my ISP, my MBP hardware or software, or my own incompetence.

Are you using wifi?
Been suffering lately, perhaps because of weather (humidity), times when many people are using the spectrum, or both (winter won't go away soon, so people stay inside and use their various wifi connected computers)

Keep a long running ping and you'll see if you have latency spikes or most maddening of all, packet loss.
I don't know the ping syntax in OS X, but in linux you can do e.g. a
Code:
ping -i 2 192.168.1.254
to continuously ping the router at two second intervals, or
Code:
ping -i 10 8.8.8.8
to ping a google DNS every 10 second. Ctrl-C to quit the program.

Bad wifi example :

Code:
64 bytes from 192.168.1.254: icmp_seq=40961 ttl=64 time=6.96 ms
64 bytes from 192.168.1.254: icmp_seq=40962 ttl=64 time=4.50 ms
64 bytes from 192.168.1.254: icmp_seq=40963 ttl=64 time=2.60 ms
64 bytes from 192.168.1.254: icmp_seq=40964 ttl=64 time=5.68 ms
64 bytes from 192.168.1.254: icmp_seq=40965 ttl=64 time=289 ms
64 bytes from 192.168.1.254: icmp_seq=40966 ttl=64 time=264 ms
64 bytes from 192.168.1.254: icmp_seq=40967 ttl=64 time=11.8 ms
64 bytes from 192.168.1.254: icmp_seq=40968 ttl=64 time=4.81 ms
64 bytes from 192.168.1.254: icmp_seq=40969 ttl=64 time=4.09 ms
64 bytes from 192.168.1.254: icmp_seq=40970 ttl=64 time=4.01 ms
64 bytes from 192.168.1.254: icmp_seq=40971 ttl=64 time=5.22 ms
64 bytes from 192.168.1.254: icmp_seq=40972 ttl=64 time=4.82 ms

packet loss : where the f... did my 6522th ping go?
by the way the TCP protocol retransmits lost packets but this can only go so far, thus half-loaded web pages (or pages stuck at the title + favicon stage sometimes)

Code:
64 bytes from 8.8.8.8: icmp_seq=6520 ttl=59 time=32.5 ms
64 bytes from 8.8.8.8: icmp_seq=6521 ttl=59 time=32.2 ms
64 bytes from 8.8.8.8: icmp_seq=6523 ttl=59 time=37.2 ms
 
Please read this whole message before doing anything.

This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

Step 1

The purpose of this step is to determine whether the problem is localized to your user account.

Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Step 2

The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, or by corruption of certain system caches.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. The question is whether Safari is still slower than other browsers.

After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.
 
Back
Top