Oct 06, 2016  I updated to Mac Sierra OS when it was released a week or two ago. Since then Chrome has been super slow. On El Capitan there was not a problem with speed. Also, when I use Chrome on Windows, or Ubuntu via Parallels, there is not a problem. It is only when using Sierra. I am thinking the problem lies with the Sierra.

Advertisement Chrome is, for many people, the first thing installed on a new MacBook. It makes sense: in its early days Chrome gained a reputation for being lightweight and fast. It was better than Safari and Firefox, people said. And it was true, at the time. It’s not the case anymore.

In fact, I’d argue that you shouldn’t use Chrome on a MacBook if you can avoid it. Over the years Chrome became a bloated program that doesn’t integrate well with OS X, and it happened so slowly most Chrome users haven’t noticed. Here are ten reasons every Mac-loving Chrome user should consider switching. Chrome Drains Your MacBook Battery Battery life has been a huge feature for Apple in recent releases of OS X. Mavericks brought energy impact measuring tools to the operating system, which you can find by clicking your battery icon right now. If you’ve got Chrome running, Chrome will show up here. It’s been said a thousand times, but it’s worth saying again: if battery life is important to you, avoid using Chrome.

Even on 4-year-old MacBooks, replacing Chrome with Safari can give you an extra hour of battery life in some cases. Google is reportedly working on the issue, and has made progress, but the job is far from finished. And you don’t have to take my word for it: open up the Activity Monitor on your Mac, then head to the “Energy” section. Open some tabs in Chrome and the same ones in another browser – Chrome will almost always use more energy for the same job.

Setting up gmail email. It’s particularly true for Netflix, if you want a test case. Your Fans Will Occasionally Sound Like Jet Engines Watching an HD video in Chrome will spin up the fans on this Macbook something crazy. What is my host for filezilla mac os10.10. Nice and cool.

— Chris Ashby (2pix)?? (@2pixelwide) The low battery life isn’t for no reason: it’s because Chrome uses more CPU power to accomplish the same thing as Safari. Partially this is because of inefficiency, and partially its because Chrome’s priority is speed. Either way, I’ve personally heard way more of my fan while using Chrome than while not. And I’m not alone. It’s kind of nuts that Chrome sets off the fans in my 2015 Macbook Pro when like Final Cut and Adobe Premier don’t — Larry Madill (@larrymadill) 3. Chrome Does Things Its Own Way, Not the Mac Way I ranted about this extensively when I talked about the reasons I hate Chrome, but it’s worth stating again: ChromeOS is the worst thing that ever happened to Chrome on other platforms.

Don’t get me wrong, ChromeOS is a great operating system, but the volume of stuff Chrome takes along with it to other platforms makes it a worse browser on the Mac. It simply doesn’t integrate with the OS well. Case in point: notifications.

Apple introduced a system-wide notifications system with Mountain Lion way back in 2012. This means notifications all look the same, never overlap each other, and can be browsed all in one archive if you miss something. Chrome could use this system, but doesn’t: it uses a completely separate notification system.