Closed Bug 425292 Opened 17 years ago Closed 16 years ago

slow browsing even on t1 connection

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: brandonj.fredrickson, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 I have a T1 connection and Firefox is very slow at loading if it does at all. I use SeaMonkey too and it does not have any problems with loading the same pages. Reproducible: Always Steps to Reproduce: 1.start firefox 2.type in any website 3.doesnt load 4. continues not to load 5. hit the go button 6. still doesnt load 7. hit go button again 8. it might work or it might not Actual Results: it worked sometimes and not others Expected Results: i expected it to load fast I am using the Aquatint Black Gloss theme 1.01 it still occurs with other themes
Version: unspecified → 2.0 Branch
Do you have any Firewalls on your system ? Does it work in the Firefox safemode ? - http://kb.mozillazine.org/Safe_Mode
No I do not have any firewalls nor does it work in safe mode.
This bug was reported using a version of Firefox that security and stability updates are no longer provided for. All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'. If you can still reproduce this bug, please provide additional details to help resolve this issue.
No reply, Please reopen if you still see this bug with firefox 3.5 or later in a new profile.
Severity: critical → normal
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.