Q: Slow browser

Hello,

Safe Boot, (holding Shift key down at bootup), & use Disk Utility from there to Repair Permissions, reboot once more.

Make a New Location, Using network locations in Mac OS X ...

http://support.apple.com/kb/HT2712

old... http://docs.info.apple.com/article.html?artnum=106653

Make a New Location, Using network locations in Mac OS X ...

http://support.apple.com/kb/HT2712

10.5, 10.6, 10.7 & 10.8…

System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.

10.5.x/10.6.x/10.7.x/10.8.x instructions...

System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.

The interface that connects to the Internet should be dragged to the top of the list.

If using Wifi/Airport...

Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.

For 10.5/10.6/10.7/10.8, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...

208.67.222.222

208.67.220.220

(There may be better or faster DNS numbers in your area, but these should be a good test).

Click OK.

Any change?

See if the Disk is issuing any S.M.A.R.T errors in Disk Utility...

http://support.apple.com/kb/PH7029

Open Activity Monitor in Applications>Utilities, select All Processes & sort on CPU%, any indications there?

How much free RAM & free Disk space do you have also, click on the Memory & Disk Usage Tabs.

Open Console in Utilities & see if there are any clues or repeating messages when this happens.

In the Memory tab of Activity Monitor, are there a lot of Pageouts?

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. Same problem?

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.