Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Safari 15 is very slow
- Thread starter radogado
- Start date
- Sort by reaction score
I visited the site above and I don’t see the same problem. Scrolling was very fast on Intel and M1 MacBook Pro. Faster than you Safari and Chrome examples.
I don’t need YouTube to notice, this POS starts out being jerky on regular pages and eventually becomes almost unusable unless periodically restarted. The performance is the worst I’ve seen in years - Safari 14 was never this bad.
Safari 15 is SLOWWWWWWW in Big Sur 11.6 on a 19,1 iMac. I go to different web sites at different speeds. Sometimes it takes a couple minutes to get there. Anyone hear of a correction for this?
Not seeing any real difference in speed. Maybe half a second. Heh.
There are some bugs but that’s what I expect from a new release of any software.
There are some bugs but that’s what I expect from a new release of any software.
I have found Safari 15.0 to be extremely slow, I am running Big Sur version 11.6 I always use Safari but I may have to switch to another browser until this issue is sorted out.
I’m finding that there is hesitation when going to some websites. iOS15 Safari seems to periodically freeze.
Yep! Safari 15.0 (16612.1.29 41.4, 16612) is horrible. I’m running macOS Big Sur 11.6 on an eight-month-old MacBook Pro 16,1 with a 2.6-GHz 6-core i7 and 32GB RAM. It starts out fine, but the longer it’s open, the slower it gets, to the point where the cursor stops and jumps and stops and jumps in every open application. Quitting Safari resolves the problem, at which point I restart it and use it until it decides to slow everything down again.
Since I’m still well within my warranty, I’ve called about this multiple times. While I generally love their support, on this particular issue, it’s been just as bad as Safari 15 itself: they just tell me to reset the NVRAM, reset the SMC, reinstall macOS Big Sur. I’ve done all of this, after which everything ran beautifully—and then I noticed that the default install included Safari 14. When Safari 15 came up in Software Update, I ignored it; but a few nights later, Big Sur decided to install it while I slept, and now I’m right back where I started. Now they want me to try it with a new user and/or in Safe Mode, which is all well and good, but I do have a full-time job that kind of needs the stuff in my account (e.g. contacts, email, chat accounts, bookmarks/browsing history, etc.).
Bad show, Apple. Please give us a decent Safari 15.1 ASAP!
Since I’m still well within my warranty, I’ve called about this multiple times. While I generally love their support, on this particular issue, it’s been just as bad as Safari 15 itself: they just tell me to reset the NVRAM, reset the SMC, reinstall macOS Big Sur. I’ve done all of this, after which everything ran beautifully—and then I noticed that the default install included Safari 14. When Safari 15 came up in Software Update, I ignored it; but a few nights later, Big Sur decided to install it while I slept, and now I’m right back where I started. Now they want me to try it with a new user and/or in Safe Mode, which is all well and good, but I do have a full-time job that kind of needs the stuff in my account (e.g. contacts, email, chat accounts, bookmarks/browsing history, etc.).
Bad show, Apple. Please give us a decent Safari 15.1 ASAP!
It is a bit better but after a short while all the bugs creep back in. And I have deleted all the blockers and disable snitch, disabled the privacy setting. What with the issues setting up the new M1 and this beta, sorely tempted elsewhere if it were not for the other OS. (I understand you take a punt on beta, user beware, awaits general release to see what is what and won't be doing it again for the first time in a ages).
Thanks for the hint! Disabling AdGuard solved it for me as well. Example: opening Google Docs with AdGuard active: 10s and 100% CPU load. With AdGuard disabled: 1s, 50% CPU load.
I don't remember that this was a problem with Safari 14 though.