How To Make Google Chrome Faster On Mac

Deleting the data from the beginning of the time is advised at this as this will free up a lot of space and make chrome faster. Update Google Chrome To Boost its Speed. Always make sure that you are using the updated version of Google Chrome. Keep a check for the latest updates regularly and install all the updates from time to time. Remove the Google Chrome download for Mac from the Downloads folder by dragging it to the Trash Now that you know how to download Google Chrome, you might want to make Chrome default browser on Mac. To do this, simply open it and click the three dots in the top-right corner, followed by Settings, then in the Default Browser section click Make. How you can speed up Google Chrome by turning off Google Chrome extensions when you don't need them. How to install and use Extensity, a free extension, to turn extensions on and off in Google Chrome without restarting Chrome. Extensity will make your life easier and your Chrome browser less cluttered.

• Make Chrome Download Faster
• Faster Google Chrome

/Mac Cleaner /Why Is Chrome So Slow on Mac? Fixes with Common Problems

I have a MacBook Pro and I love to use it for different purposes. I use it to edit photos and videos. Also, I utilize it for watching videos and checking out images. But most importantly, I use it to surf the net. So why is my browser so slow? The browser I use is Google Chrome for Mac.
But I have recently noticed that I'm having problems surfing the net using Google Chrome on my Mac. The Google Chrome running slow on Mac. How do I fix this to speed up my Google Chrome Mac?

Article GuidePart 1. Why is My Chrome Browser So Slow?Part 2. How Do I Speed up Chrome on Mac?Part 3. Common Problems Cause Chrome Running Slow on Mac (Fixed)Part 4. How to Set up Chrome?Part 5. In Conclusion

Part 1. Why is My Chrome Browser So Slow?

Google Chrome has the lion share of the market when it comes to browsers. However, it is still prone to problems. Some people experience that Chrome running slow on Mac. Sometimes, it even crashes, freezes, or refrains from loading altogether. Some people experience that pages do not load on Google Chrome anymore.

If you are having problems with Google Chrome slow on Mac, you might also have noticed that it's getting slower by the day. Why Chrome slow on Mac Catalina? The poor performance of Chrome is caused by a lot of factors. Fortunately, we have created this article to help you troubleshoot the most common problems of Google Chrome on Mac devices.

So you may want to know why is Chrome so slow on Mac, here are some of the reasons:

1. Device Battery Drains Fast.
2. Chrome Eats up Too Much of Your CPU Resources.
3. Chrome Cache or Cookies Too Much.
4. Chrome's Extensions Cause Crashing.
5. Update Of Chrome Failed.

Part 2. How Do I Speed up Chrome on Mac?

'Why is Chrome being so slow? Why is my Mac so slow after update? Why is my Mac running slow and hot? Is Chrome bad for Mac?' You may have lots of problems this time. Do you think that your Google Chrome makes MacBook hot? Before you actually fix the issue of Chrome running slow on Mac and slow MacBook, you have to make sure that the problem is not caused by your Mac device or operating system. For example, outdated system caches can result in Chrome plugins crashing altogether. This also is what causes Mac to run slow. Sometimes, It's your Mac that runs slowly and it just needs space to enhance its performance. If Mac Osx running slow is the case, you should use a tool called iMyMac PowerMyMac to delete purgeable space on Mac to free your device for space so that can speed up a slow Mac.

Here is a step-by-step guide on how to use this tool to speed up Chrome:

1. Download and launch iMyMac PowerMyMac from the official website.
2. Clicking Master Scan on the left column and scan junk file on your Mac to remove.
3. Review to select a category and select files to clean up.
4. Click Clean and wait for the cleaning process to complete.
5. Clean up is done.

Wait for the cleaning process to be complete. After it is done, it will show Zero KB for folders you have deleted. Some folders will not be marked as such because these are auto-recreated folders. It not only speeds up your Mac but also helps Chrome run fastly.

Make Chrome Download Faster

Part 3. Common Problems Cause Chrome Running Slow on Mac (Fixed)

Why is Chrome not working on my Mac? There should be some common problems you may encounter when Google Chrome too slow. You can check the solutions to Chrome running slow on Mac first:

1. Close sites or extensions within Chrome to extend the battery life.
2. Delete your Chrome cache.
3. Disable or remove Chrome extensions.
4. Checking the Internet connection.
5. Updating Chrome.
6. Restarting the Mac device.

Learn the detailed Chrome (Mac) problems and solutions to fix slow Chrome on Mac (Google Chrome not working on Mac) now.

Problem 1. Device Battery Drains Fast

Chrome is famous for having fast performance. And fast performance means it gets to use a lot of Mac's CPU resources compared to other browsers. The higher the CPU usage, the faster the battery drains. Chrome draining battery on Mac can be a problem for most users. Good performance becomes nothing if you cannot turn your Mac on because its battery is already drained.

If the battery life of your Mac is very important to you, there's a way to help you extend it. Usually, there are tabs or extensions that are eating too much of your resources and this leads to the burning of your battery life.

You can use the steps below to find the said extension or site:

1. Launch Chrome.
2. Press Settings icon.
3. Press More Tools.
4. Go to Task Manager.
5. Inside the Task Manager, sort the list by Memory.

Now, you are able to determine which site or extensions eat up most of your memory within Chrome. These sites can still be visited, although you don't need to keep them open in a specific tab if you're not going to use them. Also, even though some sites don't use up too much memory, having too many tabs open can still eat up your resources. This can lead to battery drain.

Problem 2. Browser Responsiveness Tend to Be Slow

Does browser responsiveness tend to be slow? Or even Why Google Chrome is slow and unresponsive? Why do you think is causing Chrome slow to respond and Chrome running slow on Mac? Actually, because Chrome eats up too much of your CPU resources, it tends to slow down when there is not enough resource available.

One fix for Chrome not responding Mac you can do is to involve the cache. Chrome stores your data and history with regards to web browsing in the cache. This can help speed up the surfing experience. However, when your Mac begins to wane in memory or space, it can lead to Mac slowing down and this may cause Google Chrome keeps saying page unresponsive.

Mac cleaning tools can be an easier way to clear up your browser and fix common problems associated with it. You can use the Privacy feature of iMyMac PowerMyMac.

Here's how to use it to fix Chrome running slow on Mac step-by-step:

1. Launch iMyMac PowerMyMac click on Privacy from the left column.
2. Click the Scan button to comprehensively scan browser data.
3. Preview and choose the desired browser (in this case, Chrome). And choose the various categories you want to delete on the right-hand side of the screen.
4. Press Clean and wait for the cleanup process to be complete.

Problem 3. Chrome Browser Keeps Freezing

What if your Chrome browser keeps freezing? The spinning rainbow circle appears on your device for a long time. This issuse is common especially when you continuously use your browser. What you have to do is to delete your browser cache. To fix this, you can follow the steps below.

Here's how to manually delete your Chrome cache to fix Chrome running slow on Mac issue:

1. Launch Chrome.
2. Visit Settings.
3. Go to More Tools.
4. Go to Clear Browsing Data and choose Clear Browsing Data.
5. Check the following: history, cookie, cache, and other browser data types you might want to clean up.
6. Hit Clear Browsing Data.

Problem 4. Chrome Browser Keeps Crashing

Your Google Chrome will not open on Mac? When your browser keeps crashing all the time, it's a very big issue and it states that something must be broken. But what should we do with it? Of course, we fix it. One of the common causes of crashes is Chrome's extensions. These extensions actually make our browsing experience faster or more productive. However, they can sometimes be corrupted and introduce bugs into Chrome's system thus leading to its crash.

But what should you do with problematic Chrome extensions?

First, you have to update everything. You have to ensure Chrome is actually updated to its latest version. The same goes for ALL extensions. If this didn't work or if everything is already updated to its latest version, one thing you can do is to manually turn off ALL extensions. Then, you can turn them one by one back on. In this way, you can determine which extensions are causing Chrome to crash.

Here's how to disable and/ or remove Chrome extensions manually to fix Chrome running slow on Mac issue:

1. Launch Chrome.
2. Visit Settings then visit Extensions.
3. Uncheck all extensions to disable them.
4. Close Chrome and open it again.

Once you have disabled all extensions, turn each one (one at a time). Check out to see which extension causes the crash. If you have found the one causing trouble, you can simply delete this extension by clicking the Trashcan icon located next to it in Settings > Extensions.

Problem 5. Pages Not Loading When Using Chrome

Why does Google Chrome take so long to load or even fail to load? Chrome's message when a page fails to load is: Aw snap! Why is chrome loading so slowly? There are a lot of reasons why a page fails to load in Chrome.

Here are a few fixes for Google Chrome slow to load pages, you can try to repair Chrome running slow on Mac issue:

1. Checking the Internet connection.
2. Updating Chrome.
3. Restarting the Mac device.
4. Removing Chrome Extensions (you can do this by following the steps stated in Problem #4).

When you have tried out every possible method of fixing Chrome takes too long to load and it still didn't work, you may need to reinstall or reset your Chrome browser. Don't know how to do this? Check out the next part of this guide.

Problem 6. Update Of Chrome Failed

Sometimes, Chrome just won't update on a Mac device or Chrome will slow after update. First, you have to wait for a few days before the update begins to happen. However, if it's been a week and the update still didn't push through, you might need to reset or reinstall your Chrome browser.

Here's how to manually reset your Chrome browser:

1. Open Chrome.
2. Go to Settings.
3. Scroll down and press Advanced Settings.
4. Scroll down and click Reset Settings.
5. Read the pop-up that appears and Reset.
6. Close Chrome and open it again.
7. Try the update again.

If the browser still doesn't update after this, you may have to download a specific installation file located in Chrome's official website and install it again. The installation file should be the latest.

Part 4. How to Set up Chrome?

Faster Google Chrome

After leaning the ways on how to fix Chrome running slow on Mac issue, there are still a few tweaks you can do to improve your browsing experience in Chrome. Let's check them out:

1 - Activating Prefetch

Do you want web pages to actually load faster than before? You simply have to go to Settings. Then, go to Advanced Settings and then Privacy. Ensure that 'prefetch' is activated or turned on. What happens is your resources will be kept on your system and it automatically loads a web page the next time it is visited.

2 - Utilizing Experimental Features

Chrome has hidden features---features that are currently under development. To access them, you can simply type chrome://flags. Put this in the address bar located at the top of the interface.

Press Enter afterward. Here are some of the things you can do/ have with this:

• Look for enable-smooth-scrolling and activating it to get smooth scrolling on your browser.
• Search for Number of Raster Threads. Then change it from default to 4. This will result in speeding up of image loading.
• Activate Experimental Canvas Features in order to boost loading times of pages.

Take note that you have to restart Chrome in order for the feature changes to take place. If you want to undo these changes, hit 'Reset to Default' on the page you have just entered (chrome://flags).

3 - Utilizing Shortcuts In The Browser

With just using shortcuts, your browsing experience will be faster. Learn these shortcuts on how to make Chrome faster on Mac and be amazed at how speedy your surfing experience can be:

• New Tab: Command + T
• Hide Chrome: Command + H
• Reload Page: Command + R

Other commands can be found in the official support page of Google Chrome here.

Part 5. In Conclusion

Chrome can be a great browser to use when surfing the Internet. But it is not without flaws. You can simply use this guide to fix Chrome running slow on Mac issue and the common problems you find on Mac's Chrome.

Also, you can use iMyMac PowerMyMac to fix one common Chrome problem found on Mac. If you find yourself stuck, simply go back to this guide to help solve your Chrome problems on Mac. You can also check what is making your Mac slow and use it to clean up all the junk files on your Mac to free up space and this will make your Mac run faster.

ExcellentThanks for your rating.

Rating: 4.5 / 5 (based on 70 ratings)

People Also Read:

PowerMyMac

A powerful all-in-one App for Mac

Marshal2019-10-02 07:06:11

Hello there, thanks for the tipsDoes any of the above software hold any surprises after installation, ex; only a trial version, update to pro version for this or that etc etc, cuz I am not interested just piling up software on my mac, since I have an older machine and I am running 10.10.5 on a separate note, what's your suggestion on using firefox vs chrome?please advisethanks

iMyMac2019-10-02 15:08:05

Thanks for your support! Firefox has more features and better performance while Chrome has ease-of-use and security. You can choose them to meet your different needs. But no matter which one you choose, you can use iMyMac's Browser Cleanup to speed up your browser experience. Hope this helps!

Clean up and speed up your Mac with ease

There are instructions for other platforms linked from the get the code page.

Instructions for Google Employees

Are you a Google employee? See go/building-chrome instead.

System requirements

• A 64-bit Intel Mac running 10.15.4+. (Building on Arm Macs is not yet supported.)

• Xcode 12.2+. This version of Xcode comes with ..

• The macOS 11.0 SDK. Run

  to check whether you have it. Building with a newer SDK usually works too (please fix it if it doesn't), but the releases currently use Xcode 12.2 and the macOS 11.0 SDK.

Install depot_tools

Clone the depot_tools repository:

Add depot_tools to the end of your PATH (you will probably want to put this in your ~/.bash_profile or ~/.zshrc). Assuming you cloned depot_tools to /path/to/depot_tools (note: you must use the absolute path or Python will not be able to find infra tools):

Get the code

Ensure that unicode filenames aren't mangled by HFS:

In System Preferences, check that 'Energy Saver' -> 'Power Adapter' -> 'Prevent computer from sleeping automatically when the display is off' is checked so that your laptop doesn't go to sleep and interrupt the long network connection needed here.

Create a chromium directory for the checkout and change to it (you can call this whatever you like and put it wherever you like, as long as the full path has no spaces):

Run the fetch tool from depot_tools to check out the code and its dependencies.

If you don't need the full repo history, you can save time by using fetch --no-history chromium. You can call git fetch --unshallow to retrieve the full history later.

Expect the command to take 30 minutes on even a fast connection, and many hours on slower ones.

When fetch completes, it will have created a hidden .gclient file and a directory called src in the working directory. The remaining instructions assume you have switched to the src directory:

Optional: You can also install API keys if you want your build to talk to some Google services, but this is not necessary for most development and testing purposes.

Setting up the build

Chromium uses Ninja as its main build tool along with a tool called GN to generate .ninja files. You can create any number of build directories with different configurations. To create a build directory:

• You only have to run this once for each new build directory, Ninja will update the build files as needed.
• You can replace Default with another name, but it should be a subdirectory of out.
• For other build arguments, including release settings, see GN build configuration. The default will be a debug component build matching the current host operating system and CPU.
• For more info on GN, run gn help on the command line or read the quick start guide.
• Building Chromium for arm Macs requires additional setup.

Faster builds

Full rebuilds are about the same speed in Debug and Release, but linking is a lot faster in Release builds.

Put

in your args.gn to do a release build.

Put

in your args.gn to build many small dylibs instead of a single large executable. This makes incremental builds much faster, at the cost of producing a binary that opens less quickly. Component builds work in both debug and release.

Put

in your args.gn to disable debug symbols altogether. This makes both full rebuilds and linking faster (at the cost of not getting symbolized backtraces in gdb).

CCache

You might also want to install ccache to speed up the build.

Build Chromium

Build Chromium (the 'chrome' target) with Ninja using the command:

(autoninja is a wrapper that automatically provides optimal values for the arguments passed to ninja.)

You can get a list of all of the other build targets from GN by running gn ls out/Default from the command line. To compile one, pass the GN label to Ninja with no preceding '//' (so, for //chrome/test:unit_tests use autoninja -C out/Default chrome/test:unit_tests).

Run Chromium

Once it is built, you can simply run the browser:

Avoiding the 'incoming network connections' dialog

Every time you start a new developer build of Chrome you get a system dialog asking 'Do you want the application Chromium.app to accept incoming network connections?' - to avoid this, run with this command-line flag:

--disable-features='MediaRouter'

Running test targets

You can run the tests in the same way. You can also limit which tests are run using the --gtest_filter arg, e.g.:

You can find out more about GoogleTest at its GitHub page.

Debugging

Good debugging tips can be found here. If you would like to debug in a graphical environment, rather than using lldb at the command line, that is possible without building in Xcode (see Debugging in Xcode).

Tips for printing variables from lldb prompt (both in Xcode or in terminal):

• If uptr is a std::unique_ptr, the address it wraps is accessible as uptr.__ptr_.__value_.
• To pretty-print base::string16, ensure you have a ~/.lldbinit file and add the following line into it (substitute {SRC} for your actual path to the root of Chromium's sources):

Update your checkout

To update an existing checkout, you can run

The first command updates the primary Chromium source repository and rebases any of your local branches on top of tip-of-tree (aka the Git branch origin/master). If you don't want to use this script, you can also just use git pull or other common Git commands to update the repo.

The second command syncs dependencies to the appropriate versions and re-runs hooks as needed.

Tips, tricks, and troubleshooting

Using Xcode-Ninja Hybrid

While using Xcode is unsupported, GN supports a hybrid approach of using Ninja for building, but Xcode for editing and driving compilation. Xcode is still slow, but it runs fairly well even with indexing enabled. Most people build in the Terminal and write code with a text editor, though.

With hybrid builds, compilation is still handled by Ninja, and can be run from the command line (e.g. autoninja -C out/gn chrome) or by choosing the chrome target in the hybrid project and choosing Build.

To use Xcode-Ninja Hybrid pass --ide=xcode to gn gen:

Open it:

You may run into a problem where http://YES is opened as a new tab every time you launch Chrome. To fix this, open the scheme editor for the Run scheme, choose the Options tab, and uncheck 'Allow debugging when using document Versions Browser'. When this option is checked, Xcode adds --NSDocumentRevisionsDebugMode YES to the launch arguments, and the YES gets interpreted as a URL to open.

If you have problems building, join us in #chromium on irc.freenode.net and ask there. Be sure that the waterfall is green and the tree is open before checking out. This will increase your chances of success.

Improving performance of git status

Increase the vnode cache size

git status is used frequently to determine the status of your checkout. Due to the large number of files in Chromium‘s checkout, git status performance can be quite variable. Increasing the system's vnode cache appears to help. By default, this command:

Outputs kern.maxvnodes: 263168 (263168 is 257 * 1024). To increase this setting:

Higher values may be appropriate if you routinely move between different Chromium checkouts. This setting will reset on reboot, the startup setting can be set in /etc/sysctl.conf:

Or edit the file directly.

Configure git to use an untracked cache

If git --version reports 2.8 or higher, try running Free serial key for microsoft office 2011 mac.

If the output ends with OK, then the following may also improve performance of git status:

If git --version reports 2.6 or higher, but below 2.8, you can instead run

Xcode license agreement

If you're getting the error

Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.

the Xcode license hasn't been accepted yet which (contrary to the message) any user can do by running:

Only accepting for all users of the machine requires root: