User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060726 BonEcho/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060726 BonEcho/2.0b1 Firefox is slow to display pages on www.bigfootcomputers.com I believe this is script-related, because disabling scripting (using the NoScript extension) solves the problem -- but then the site's functionality is severely reduced. Reproducible: Always Steps to Reproduce: 1. Go to www.bigfootcomputers.com with scripting enabled Actual Results: The page is partially displayed, then Firefox seems to freeze for several seconds, then the page is displayed properly and works properly. Expected Results: Long delays during page load/display shouldn't happen. This is especially annoying on slow systems, e.g. Pentium III 1GHz. It's less noticeable, but still annoying, on faster systems, e.g. AthlonXP 2500+. I don't think this bug is platform-specific, as I've seen it on both Windows and Linux. I'm running a Bon Echo nightly as I write this, but this bug also affects Firefox 1.5.
URL gives me a 403 Forbidden message
That's very strange. It works fine for me. Could you try it again, or could someone else try it?
I tried Venkman's profiling feature. It clearly pointed the blame at: http://www.bigfootcomputers.com/Merchant2/menus/transmenuC.js That script is originally from here: http://youngpup.net/2004/transmenus/project
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 5-15-2010]
Version: unspecified → 2.0 Branch
You might as well go ahead and close this bug. The website on which I originally noticed the problem no longer exists.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.