sehix said:
Newegg would probably come up faster if you tried http:// instead of htpp:// in your link.
Uhh, what are you talking about? (fixed, thanks
😀)
Seriously, there may be more of an issue with your ISP than with Safari itself; both sites pop up quickly, and navigation is unexceptional here, whether on an intel iMac, or a Mini.
Nope. ISP is fine, and plenty of other sites with similar complexity load quite fast in Safari. I don't just mean it's slow, which could be more of a network issue than anything else. It takes a huge amount of CPU time to render these sites, resulting in a nice beachball while I wait for my page. At home I'm on a 733 MHz G4, and it's ridiculously slow - well over a minute burning full CPU to render a page with lots of stuff listed.
Just for fun, I did a little test on a dual 2.0 G5 here at work (Panther Server, Safari 1.2.4). Using the unix 'top' program, I watched total CPU usage as Safari loaded the main NewEgg page. It used 10 seconds of 2.0 GHz G5 CPU time. Not just 10 seconds real time, but 10 seconds CPU time. Firefox 1.5.0.1 takes 2.4 seconds on the same machine, and renders the page more correctly too. To be fair, I don't recall the same rendering bug on Safari 1.3 and up, but I don't have that in front of me right now.
This page, listing 100 items, is even worse. Safari took 22 seconds of CPU time to render it on the G5. Just imagine how slow it is on my G4! Firefox took 6 seconds on the G5.
Obviously these sites may have needless complexities in their HTML, since others with similar layouts render much faster on both browsers. Good thing Steve didn't use NewEgg or Best Buy to demonstrate how Safari on the Intel iMac is "instant." I'm sure it's fast, but nowhere near instant on these sites.
And yeah, the G4 was low end when I bought it 4 years ago, but it's still quite snappy for the vast majority of websites, so I wouldn't blame it on an old machine. All I'm saying is that Safari still has plenty of room for improvement. And with open source contributors continuing to refine kHTML and therefore WebKit, I'm hoping it'll get there. MacBooks as thanks won't hurt. (yay, finally back on the main topic here)
😉