Michael Fessenden

Q: Google search from Safari is slow

I'm running Safari 9.0.3 with El Capitan 10.11.3 on a new Macbook Pro Retina 15" and having a lot of trouble searching from the Safari address bar. Probably 50-75% of the time when I type something into the search bar to perform a Google search, the search hangs for a very long time, or just times out. At first I thought it might be a problem with my home network, but it's happening when I travel as well. Going to google and searching is faster, but often Safari hangs after I type in "google.com".

 

I've tried several fixes to no avail:

 

- changing the search engine in Safari preferences

- disabling all of my extensions

- disabling all of my plugins

- turning off "Include search engine suggestions"

- setting my DNS to OpenDNS & Google's DNS

- disabling DNS prefetching

- deleting my history

- deleting ~/Library/Caches/com.apple.Safari/Cache.db

- deleting ~/Library/Caches/Metadata/Safari

- deleting Safari's preferences

 

If anyone knows of something else that might work, I'd be very appreciative, so far my efforts seem to be making the problem worse

MacBook Pro (Retina, 15-inch, Mid 2015), OS X El Capitan (10.11.3)

Posted on Mar 8, 2016 4:42 PM

Close

Q: Google search from Safari is slow

  • All replies
  • Helpful answers

  • by Linc Davis,Solvedanswer

    Linc Davis Linc Davis Mar 8, 2016 6:35 PM in response to Michael Fessenden
    Level 10 (207,995 points)
    Applications
    Mar 8, 2016 6:35 PM in response to Michael Fessenden

    Please 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.

    Test. After testing, restart as usual and post the results.

  • by Michael Fessenden,

    Michael Fessenden Michael Fessenden Mar 8, 2016 6:42 PM in response to Linc Davis
    Level 1 (34 points)
    Applications
    Mar 8, 2016 6:42 PM in response to Linc Davis

    Thanks for the reply.

     

    I booted up in recovery and everything works as expected, so there must be something going on with my setup.

     

    On another note, I somehow marked this as 'solved' and can't seem to undo it.

  • by Linc Davis,

    Linc Davis Linc Davis Mar 8, 2016 6:53 PM in response to Michael Fessenden
    Level 10 (207,995 points)
    Applications
    Mar 8, 2016 6:53 PM in response to Michael Fessenden

    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 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. 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, by a font conflict, or by corruption of the file system or of certain system caches.

    Please take this step regardless of the results of Step 1.

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup 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. Same problem?

    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

  • by Michael Fessenden,

    Michael Fessenden Michael Fessenden Mar 9, 2016 7:13 AM in response to Linc Davis
    Level 1 (34 points)
    Applications
    Mar 9, 2016 7:13 AM in response to Linc Davis

    Thanks again.

     

    I logged into a guest account...no problems there. Restarted into safe mode and didn't notice any slowness either.

  • by Linc Davis,

    Linc Davis Linc Davis Mar 9, 2016 7:40 AM in response to Michael Fessenden
    Level 10 (207,995 points)
    Applications
    Mar 9, 2016 7:40 AM in response to Michael Fessenden

    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.

  • by Michael Fessenden,

    Michael Fessenden Michael Fessenden Mar 18, 2016 9:32 AM in response to Linc Davis
    Level 1 (34 points)
    Applications
    Mar 18, 2016 9:32 AM in response to Linc Davis

    Sorry for the delay getting back to you, I had to travel last week. I ran the script and got the results which I've posted here:

     

    http://pastebin.com/G4p3zKXS

     

    Let me know if anything is missing.

  • by Linc Davis,

    Linc Davis Linc Davis Mar 19, 2016 9:52 AM in response to Michael Fessenden
    Level 10 (207,995 points)
    Applications
    Mar 19, 2016 9:52 AM in response to Michael Fessenden

    A

    Some of your user files (not system files) have incorrect permissions or are locked. This procedure will unlock those files and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.

    Please back up all data before proceeding.

    Step 1

    If you have more than one user, and the one in question is not an administrator, then go to Step 2.

    Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):

    sudo find ~ $TMPDIR.. -exec chflags -h nosappnd,noschg,nosunlnk,nouappnd,nouchg {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-

    You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

    The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.

    Step 2 (optional)

    Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.

    Start up in Recovery mode. You may be prompted to select a language, then the OS X Utilities screen will appear.

    If you use FileVault 2, select Disk Utility, then select the icon of the FileVault startup volume ("Macintosh HD," unless you gave it a different name.) It will be nested below another drive icon. Click the Unlock button in the toolbar and enter your login password when prompted. Then quit Disk Utility to be returned to the main screen.

    Select

              Utilities Terminal

    from the menu bar. A Terminal window will open. In that window, type this:

    resetp

    Press the tab key. The partial command you typed will automatically be completed to this:

    resetpassword

    Press return. A Reset Password window will open. You’re not going to reset a password.

    Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.

    Select your username from the menu labeled Select the user account if not already selected.

    Under Reset Home Directory Permissions and ACLs, click the Reset button.

    Select

               Restart

    from the menu bar.

    B

    You've installed many Safari extensions. I'm taking your word for it that you have ruled them all out as suspects. If my assumption is wrong, the problem may not be solved.

    C

    Please sign out of iCloud in its preference pane and see whether there's any change. No data will be removed from the servers, and you can retrieve it by signing back in. That said, you should always have a current archive of the data for safety's sake, even if you don't sign out.

    If you use iCloud Keychain, when you sign back in to iCloud follow one of the procedures described in this support article to set it up on an additional device.

    D

    The third-party software "TheFoundry" has a license manager that isn't working. I don't know whether that issue is related to the one you asked about. You would have to refer to the developer for support, or remove the software if you don't need it.

    E

    "BitTorrent" could at times be using a lot of network bandwidth and slowing everything else down, but it wasn't doing that when you ran the test.

    F

    You're using Google DNS, which I don't recommend for more than temporary use. It's usually best to use the DNS service provided by your ISP. If you still have problems after taking the above steps, see below.

    Unlock the Network preference pane, if necessary, by clicking the lock icon in the lower left corner and entering your password.

    Cllck Advanced and select the TCP/IP tab in the sheet that drops down. Near the top, you'll most likely see this:

               Configure IPv4: Using DHCP

    If that's not what you see, stop here and ask for instructions.

    Otherwise, select the DNS tab and delete all the DNS Servers from the list on the left by selecting them and clicking the minus-sign button below. Click OK, then Apply.

    Select the DNS tab again. The server list should have been automatically repopulated with at least one address, and you should have normal Internet access. If so, you can close the preference pane.

    If the server list is empty, go back to the TCP/IP tab and click

                Renew DHCP Lease

    Check the DNS server list again. If it's still empty, click the plus-sign button and enter this:

                8.8.8.8