Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Safari slow after last El Capitan update

Hello!


After the last El Capitan update (on April 16), Safari has been slow. For example, going from one URL to another used to take a second or two and now takes up to 15 seconds. I first thought my cable provider was the culprit but then I tried a different browser (Firefox) and it's never slow, even when Safari is still waiting to load a page.


I also noticed that nsurlstoraged in Activity Monitor is consuming a large amount of CPU when I am running Safari but not when I am running Firefox.


I tried disabling all the extensions in Safari as well as disabling login items (in case there was a conflict somewhere) but that didn't fix the problem.


I really prefer Safari over Firefox but for the time being I need to run Firefox just to get work done.


Any thoughts on where to go from here?


Thanks in advance for your help.




Armand

MacBook Pro, OS X El Capitan (10.11.4)

Posted on Apr 26, 2016 7:28 AM

Reply
11 replies

Apr 26, 2016 7:33 AM in response to ArmandG

Troubleshoot Safari plug-ins .. (not the same as Extensions)



Go to Safari > Preferences. This time select the Security tab. Deselect: Allow plug-ins. Quit and relaunch Safari to test.


If that made a difference, instructions for troubleshooting plugins here.

If that doesn't help the nsurlstoraged process, try resetting the SMC as mentioned in a similar discussion here > CPU Load from NSURLSTORAGED

Apr 26, 2016 8:25 AM in response to ArmandG

There are many possible causes for problems with web browsing. Below are some simple steps that may either solve the problem or point the way to a solution.

Please back up all data before making any changes.

1. Restart your router and also your broadband device, if they're separate.

2. If you connect to the the router with Wi-Fi, turn Wi-Fi off and then back on.

3. If you connect with Wi-Fi and you can also connect with Ethernet, do that and turn off Wi-Fi.

4. Take the steps recommended in this support article.

5. If the Downloads button (with the icon of a downward-pointing arrow) is showing in the toolbar, click it and then click Clear in the box that appears. The download history will be removed.

6. In the Security tab of the preferences window, uncheck the box marked

Warn when visiting a fraudulent website

if it's checked.

7. If you're running OS X 10.10 or later, select the Search tab. Uncheck the box marked

Enable Quick Website Search

if it's checked.

8. If you're running OS X 10.9 or later, select the Advanced tab and uncheck the box marked

Stop plug-ins to save power

Quit and relaunch the browser.

9. Select the Security tab and uncheck the box marked

Allow WebGL

if it's checked. If it's not checked, check it.

10. If you're running OS X 10.10 or later, open the General pane in System Preferences and uncheck the box marked

Allow Handoff between this Mac and your iCloud devices

if it's checked.

11. 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 documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; 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.

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.

12. Are any other web browsers installed, and are they the same? What about other Internet applications, such as iTunes and the App Store?

13. If other browsers and Internet applications are also affected, follow these instructions and test.

14. Open the iCloud preference pane and uncheck the boxes marked Safari and Photos, if they're checked.

15. Are there any other devices on the same network that can browse the Web, and if so, are they affected?

16. If you can, test Safari on another network.

17. If you know that you've modified the hosts file to block access to certain servers, undo that modification.

18. Start up in Recovery mode. In the OS X Utilities screen, select Get Help Online. A clean copy of Safari will launch. No plugins, such as Flash, will be available. While in Recovery, you'll have no access to your saved bookmarks or passwords, so make a note of those before you begin, if they're needed for the test.

After testing, restart as usual.

Apr 26, 2016 2:38 PM in response to Linc Davis

Hi Linc,


Thanks for the info. I went through each step but none made a difference.


Keep in mind that the problem (slow browsing) is only when I am using Safari. The notebook gets very warm and the fan is running at max RPM (which is expected given the computer is running hot).


If i quit Safari and start using Firefox then the fan slows down and the computer cools down. I also noticed that once I quit Safari and am using Firefox that nsurlstoraged goes from almost 100% CPU utilization to between 1% and 5%.


It also all started when I updated El Capitan to 10.11.4 on April 16.


Any other thoughts? I really appreciate the assistance.



Armand

Apr 26, 2016 7:05 PM in response to Linc Davis

Sorry for the oversight on #18.


Of course while in Recovery mode I didn't have access to Activity Monitor so I can't tell you how much resource was being used by nsurlstoraged, but Safari worked fine. The computer never got hot (like it does when running in normal mode).


Not such where the conflict is. Problem still exists with extensions, plugins, and login items disabled. The problem also exists when running is safe mode.




Armand

Apr 26, 2016 7:21 PM in response to ArmandG

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

The test works on OS X 10.8 ("Mountain Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.

You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

4. Here's a general summary of what you need to do, if you choose to proceed:

☞ Copy the text of a particular web page (not this one) to the Clipboard.

☞ Paste into the window of another application.

☞ Wait for the test to run. It usually takes a few minutes.

☞ Paste the results, which will have been copied automatically, back into a reply on this page.

These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

8. Launch the built-in Terminal application in any one of the following ways:

☞ Enter the first few letters of its name ("Terminal") into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

Test started

Part 1 of 4 done at: … sec

Part 4 of 4 done at: … sec

The test results are on the Clipboard.

Please close this window.

The intervals between parts won't be exactly equal, but they give a rough indication of progress.

Wait for the final message "Please close this window" to appear—again, usually within a few minutes. If you don't see that message within about 30 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something.

In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

11. When the test is complete, or if you stopped it manually, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Apr 27, 2016 7:06 PM in response to Linc Davis

Hi Linc,


Apologies for not replying sooner. Had a long day at work. 😐


When i returned home from work I went online with Safari and all is working well. Safari is running as fast as it used to and Activity Monitor shows that nsurlstoraged is using less than 2% of CPU. Computer also not running hot. Been online for the past 2 hours and everything has been working fine.


I didn't change anything and didn't even reboot the computer (I put the computer in sleep mode at night).


I will keep an eye on this and will run your script once Safari starts acting up again.


Thanks for your help.




Armand

May 1, 2016 10:22 AM in response to Linc Davis

Hi Linc,


This is very strange. This is now Day 4 that Safari has been working well. No slow down and nsurlstoraged is using less than 1% of CPU.


Granted, I haven't been using the computer as much (been very busy at work) but the problem has exhibited itself usually within a few minutes of using Safari.


I tried rebooting the computer (thinking that perhaps I terminated an app that was conflicting and rebooting would restart it) and that hasn't changed anything.


Any thoughts as to why things are now working well?


Again, thanks for your help. It is very much appreciated.




Armand

Safari slow after last El Capitan update

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.