EarlRay

Q: my browser is slow. can you help pl.

I have running multiple tabs on several Safari windows on the go.

Would this be a factor why my browser is running slow and sometimes seizes up and I have to restart my laptop.

MacBook Pro (15-inch Mid 2010), iOS 8

Posted on Jul 27, 2015 2:09 AM

Close

Q: my browser is slow. can you help pl.

  • All replies
  • Helpful answers

  • by D.Cohen,

    D.Cohen D.Cohen Jul 27, 2015 2:35 AM in response to EarlRay
    Level 6 (8,424 points)
    Desktops
    Jul 27, 2015 2:35 AM in response to EarlRay

    If you have problems opening webpages or if your Safari browser is slow, take a look at these troubleshooting techniques suggested by Apple.

    https://support.apple.com/en-us/HT204098


    Go to Safari menu (At the very top right side of your screen next to Apple icon), choose "Quit Safari"

    press "Shift" button and while holding this button on your keyboard single click on the Safari icon on your Dock.


    Open Safari - Preferences - Privacy - Remove All Website Data.


    Open the Go menu with Option (Alt) key pressed - Library - locate Safari folder and move it to your desktop.


    Also, you may try this:


    - Shut down your Mac

    - Wait until your computer turns off and after that press the Power button

    - Right after you hear the startup tone, press and hold the Shift key

    - Release the Shift key when you see a grey Apple sign and the progress bar below this sign

    - Once you see Desktop, start a Disk Utility scan to detect and repair file system errors (don't forget to choose your main hard drive)

    - Click on Verify Disk and then, if asked to fix problems, on Repair Disk

    - After this, click on Verify Disk Permissions and then on Repair Disk Permissions

    - After the process is finished, shut down your Mac and turn it back on after about 30 seconds


    Hope this helps!

  • by dominic23,

    dominic23 dominic23 Jul 27, 2015 2:35 AM in response to EarlRay
    Level 8 (42,122 points)
    Mac OS X
    Jul 27, 2015 2:35 AM in response to EarlRay

    1. Delete Caches.db

     

        Close all windows and quit all applications.

        Hold "option" key down and click "Go" menu in the Finder menu bar.

        Select "Library" from the dropdown.

     

        Library > Caches > com.apple.Safari > Caches.db

        Right click the Caches.db file and select "Move To Trash.

        Close windows and relaunch Safari.

     

    2. Empty Caches

        Safari > Preference > Advanced

        Checkmark the box for "Show Develop menu in menu bar".

        Develop menu will appear in the Safari menu bar.

        Click Develop and select "Empty Caches" from the dropdown.

     

    3. Delete Cookies

        Safari > Preferences > Privacy > Cookies and other website data:

        Click the “Details” button.

        Remove all cookies except  ones from Apple, your internet service provider and banks.

     

    4. Safari > Preferences > Extensions

        Turn off Extensions if any and launch Safari again to test.

        Turn on those one by one and test.

     

    Do you have any anti-virus software installed?

  • by OGELTHORPE,

    OGELTHORPE OGELTHORPE Jul 27, 2015 4:39 AM in response to EarlRay
    Level 9 (52,793 points)
    Mac OS X
    Jul 27, 2015 4:39 AM in response to EarlRay

    Check to see if you MBP has had kernel panics.  Use these instructions:

     

    https://support.apple.com/en-us/HT201753

     

    If so, log and post it.

     

    Ciao.

  • by Linc Davis,

    Linc Davis Linc Davis Jul 27, 2015 7:26 AM in response to EarlRay
    Level 10 (208,044 points)
    Applications
    Jul 27, 2015 7:26 AM in response to EarlRay

    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.