On Safari 5.1 performance issues

Lately I have noticed an interesting trend, both on Twitter and on some blogs I read on a regular basis: people complaining about Safari 5.1 performance. Many seem to agree that it has noticeably worsened compared with Safari 5.0.x. Some also add that Google Chrome, in their experience, is noticeably faster than Safari.

Tim Bray:

For some years, Safari has been my default browser. I generally prefer its choices in framing and ergonomics and shortcuts over all others. But I’ve had to stop using it.

Via John Gruber, who added:

I’m seeing the same things Bray is with Safari for Mac, particularly the performance problems when you have a lot of windows and tabs open.

Via Marco Arment, who added:

I’m also frustrated by the same performance problems with Safari 5.1 on Lion, although it was similar on Snow Leopard as of my (relatively late) Lion upgrade two weeks ago.

I don’t even have Flash installed, so I can’t blame that: Safari 5.1 is just incredibly slow in general web rendering, scrolling, and other interactions. It’s a huge regression from the performance of Safari 5.0, and feels even slower than Mobile Safari on my iPad 2 at times.

I have to say that — while I too have noticed a general worsening of Safari 5.1’s performance compared with Safari 5.0.x (or even with Safari 4.x on Mac OS X Tiger, for that matter) — I can’t say that my user experience with Safari has become ‘frustrating’. It still feels responsive as regards to scrolling and other interactions. Furthermore, on my system I haven’t noticed this evident performance gap between Chrome and Safari other people are claiming. 

Of course there are some variables at play, and I guess these differences depend on system configuration and browser usage. Since upgrading to Safari 5.1, the only mildly annoying thing I have noticed is the infamous ‘page reloading’ issue where sometimes, when jumping to another tab, the previously loaded webpage doesn’t appear to be cached and is force-reloaded. For this matter I lost a long comment I was posting on a blog: I opened another tab to check an article and a link to corroborate what I was writing, returned to the comment page and Safari told me that it wasn’t responding and that it had to force-reload it.

So yes, annoying, but apart from this I haven’t felt Safari to be remarkably slower than the previous version or than Google Chrome. And I usually have at least 8–9 tabs open. For the sake of comparison, here’s some more information about my system: my main Mac is a 15-inch MacBook Pro (mid-2009, 2.66 GHz Core 2 Duo). I’m still using Snow Leopard (10.6.8, fully updated). I have disabled Flash entirely, except from the built-in plugin in Google Chrome. Also worth noting is that I use Safari without extensions. Another thing worth mentioning is that Safari feels somewhat more stable after disabling the caches (Develop > Disable Caches), which actually sounds paradoxical if you consider the force-reload issue mentioned above. It’s just a feeling though, one of the things you try while troubleshooting. I’m not saying that disabling caches is an effectual remedy. It may depend on something entirely different.

It would be interesting to know about your experience with Safari 5.1 (if it’s your main browser). Give some feedback if you like, and let’s see how your mileage varies.

Category Software Tags ,

About Riccardo Mori

Writer. Translator. Mac consultant. Enthusiast photographer. • If you like what I write, please consider supporting my writing by purchasing my short stories, Minigrooves or by making a donation. Thank you!