Closed Bug 267393 Opened 20 years ago Closed 19 years ago

FF Loads Most PAges Much Slower than Safari on OS X.3.5

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

()

RESOLVED EXPIRED

People

(Reporter: mail, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 I was expecting much better performance, as per newspaper articles and postings but, just FYI, on a decent broadband connection, using same Mac, some pages take 5x as long to load as Safari which, itself can take awhile to load. This is scientific: I've loaded URL into both browsers, then hit GO (or hit ENTER) asa fast as possible and FF just sits there and I dont think it's site specific. Reproducible: Sometimes Steps to Reproduce:
Are you sure the caching isn't influencing it?? If you put the same URL into both browsers that you've been to before, safari probably has both the DNS cached already and the page.. (In reply to comment #0) > User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 > Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 > > I was expecting much better performance, as per newspaper articles and postings > but, just FYI, on a decent broadband connection, using same Mac, some pages take > 5x as long to load as Safari which, itself can take awhile to load. > > This is scientific: I've loaded URL into both browsers, then hit GO (or hit > ENTER) asa fast as possible and FF just sits there and I dont think it's site > specific. > > Reproducible: Sometimes > Steps to Reproduce:
Mark this CRITICAL! Not minor. There is a serious usability problem with Firefox (at least on Mac OS X), and no attention has been paid to this serious bug report for TWO MONTHS. That is pathetic. I'm going to abandon Firefox if this isn't resolved soon and I'm sure many others will as well. Safari and Opera are serious and responsibly developed applications which respond well to user input. Hopes for Firefox were high, but it seems that more attention is paid to pretty "foxy" graphic design rather than performance, responsiveness, and usability. Firefox is not at all responsive. It consistently takes 3-10 seconds to open a new tab, and during that time the user cannot switch to other Firefox tabs or windows. The colorwheel starts spinning and Firefox will not accept any other user input. This wasn't as noticable prior to the 1.0 release. Or maybe it was, but users wrote it off as pre-release sloppiness. Firefox's performance (on OS X, AlBook 15" G4) is horrible. Please try releasing again, this time focus on releasing a responsive, well performing, usable browser. Thank you.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.