Just up front, one thing to remember with FireFox is that it's currently in the developmental stages, i.e. not even the 1.0 version. It's rather amazing to me it works as beautifully as it does at this point, but anyway. It can take some tweaking to get things to work the way you want them to on specific systems, and some of this advice is definitely system dependent. But, overall, there is absolutely no reason why FireFox should not do things generally faster than IE.
A couple questions. I'll offer suggestions before waiting for the answers since you may not be reading at the moment, but I can try to go into more detail based on your answers if need be.
1) Do you know what the user.js file is, and have you created one? If you don't have one, make one. It's just a text file that should be placed in your profile directory. If you are using at least version .9, assuming a standard, personal Windoze environment setup with your application files on drive C:, you will place this in :
C:\Documents and Settings\
YOUR USER NAME\Application Data\Mozilla\Firefox\Profiles
You will have another directory called something like default.xxx (the extension is randomly generated) in the Profiles directory. Open that and create user.js there. There will be a number of other files and directories there also. This is where FireFox keeps all its data specific to you.
Just open up Notepad and save a plain text file named user.js
BTW, by default, the "application data" file is hidden by Windoze. You'll have to make sure the "show hidden files folders" setting under the Tools/Folder Options/View is checked in order to see that directory.
Now, add these lines to the file:
user_pref("network.http.pipelining", true);
user_pref("network.http.pipelining.firstrequest", true);
user_pref("network.http.pipelining.maxrequests", 8);
user_pref("nglayout.initialpaint.delay", 0);
user_pref("content.notify.backoffcount", 5);
user_pref("plugin.expose_full_path", true);
user_pref("ui.submenuDelay", 0); 2) The following is based on a combination of your connection speed and system configuration, i.e. memory and speed. All this is relative. "Fast" connection basically means at least DSL. "Fast" computer speed basically means anything running over 1.2GHZ with better than recommended memory for running Windoze XP (256MB). This could also be affected by your drive speed, even your graphics card, but it would be insane to try to tweak it with all these factors in mind. Processor and memory are the most important for this.
IF you have a fast connection and a fast computer, add these lines:
user_pref("content.interrupt.parsing", true);
user_pref("content.max.tokenizing.time", 2250000);
user_pref("content.notify.interval", 750000);
user_pref("content.notify.ontimer", true);
user_pref("content.switch.threshold", 750000);
user_pref("nglayout.initialpaint.delay", 0);
user_pref("network.http.max-connections", 48);
user_pref("network.http.max-connections-per-server", 16);
user_pref("network.http.max-persistent-connections-per-proxy", 16);
user_pref("network.http.max-persistent-connections-per-server", 8);
user_pref("browser.cache.memory.capacity", 65536);
If you have some other setup, I'll just end by suggesting you go to the following site, where I originally got most of this:
http://www.tweakfactor.com/articles/tweaks/firefoxtweak/4.htmlIf you read through the page, you'll note some other things, including a nice little tweak for the user.js file that prevents those media windows that open to display pics, vids, sound browsers, etc. from cutting out the tabs and menu bars.
Anyway, after you've added whatever you're going to add to the user.js file, save it, close it, and restart FireFox. If this doesn't speed things up, there is some other problem than just the program itself.
OnEdit: BTW, one of the things that may make it seem as though FF is running slower than IE is that IE displays images as they are loading. The default for FF is not to display images until after they are loaded. In pages with large images this can make the entire page seem to be loading slowly, especially on slower connections. You can alter this via the user.js file as well. Follow the link leading backwards on the page listed above for the code to add.