Forum Moderators: open

Message Too Old, No Replies

Why is Firefox faster than IE?

and how does on tune pages to load faster in IE

         

Namaste

5:40 pm on Aug 18, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I having some speed issues with a new site I'm launching. I think we bothched some hardware and it's pretty slow.

To add salt on the wound, we have been testing all week in Firefox (like idiots), and decided to live with the poor speed for a few weeks and then overhaul the hardware after doing some other tweeks.

But then we started testing in IE. And the site is remarkably slower(2-3 seconds). Infact it's so slow in IE that we will not be able to launch it as scheduled.

I am wondering why it's so slow in IE.

I'm also looking for a quick fix for IE that will bring it somewhere near FF.

Ps. the pages are CSS & PHP on Linux & Apache

tedster

7:17 pm on Aug 18, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Except for any server issues that you may need to iron out (and that might include time-consuming database queries) the first thing to check is the total file size of your html document PLUS all the related files - images, external css, external javascript calls. This total is sometimes called the "total page weight" and will be the principle determination of download speed when the server is functioning well.

Since you are using FireFox, there is a "Developers Extension" you can install that offers a speed report -- it may give you some more ideas.

asquithea

7:52 pm on Aug 18, 2005 (gmt 0)

10+ Year Member



I've generally found IE to be less responsive to clicks, giving it a slower "feel" than Firefox. But if two or three additional seconds is making your site unusable, I guess your performance problems were pretty bad to start with.

You definitely need to profile your system. Some thoughts:

As tedster said, database queries can be a serious weak point. You should be opening a connection to the database only once per page. Look carefully at your queries to make sure that you're using indexes appropriately, and that you aren't joining massive amounts of data unnecessarily.

I'd also suggest looking over your table-locking routines if the site accepts much user data, but in this case it sounds as if it isn't user load that's the problem.

Add time-monitoring code to your scripts so you can tell which parts of the page are taking longest to generate. Obviously, bracket the database calls, but do cover the rest of the script as well.

You can get an HTTP headers extension for Firefox. This should give you some idea about the data flowing back and forth between browser and server. Are your caching indications set correctly, or is the browser repeatedly fetching data that hasn't changed? You can probably get much of this information for IE from the Apache logs.

Namaste

8:02 am on Aug 19, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



thanks, am on it.

Still don't understand why IE is taking 2-3 seconds longer to load "first byte in browser"

haggul

8:54 am on Aug 19, 2005 (gmt 0)

10+ Year Member



It's probably just a slower rendering engine - that's all.

Like the way Opera was always faster than IE, and IMHO Netscape was always slowest of them all!

Namaste

9:18 am on Aug 19, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



are there any IE specific parameters that can be tweaked server side to make pages faster?

tedster

2:21 pm on Aug 19, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The last benchmark tests I saw for comparative rendering speeds show that the only significant difference between IE Windows and Firefox Windows is in the parsing of scripts - that's where IE is a good bit slower. I think the big factor here is all the security fixes that are tacked on to IE's script parsing.

So, by any chance is this page script-heavy?

Namaste

2:39 pm on Aug 19, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



not those kind of scripts.

Namaste

12:18 pm on Aug 20, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



one of the problems that is pronounced in IE is that when the browser back button is clicked, instead of being instant, it takes the same amount of time as if a fresh link was clicked.

My pages have some dynamic content on them, is it because of this?

encyclo

12:42 am on Aug 21, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Still don't understand why IE is taking 2-3 seconds longer to load "first byte in browser"

If I understand it correctly you think that it is during page generation server-side that there might be a problem? Have you tried the Live HTTP headers extension in Firefox to record the headers for a pageview? Also, just to confirm are you using any heavy client-side stuff? Are you feeding different CSS to IE via conditional comments? No .htc files or similar? Are you running Norton Internet Security or similar transparent proxy/adblocking program on your IE test machines, and if you are and you turn it off, does it make a difference?

Kyle2911

10:14 am on Aug 22, 2005 (gmt 0)

10+ Year Member



You guys have probably seen this before, but I thought I'd post a link anyway:

[howtocreate.co.uk...]

Namaste

12:10 pm on Sep 5, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



to continue this topic, what we have found to be the chief differance between IE and Firefox is the way the browsers handle "dynamic" content:

- Firefox avoids database trips for content it already has. Example, on a shopping site, with several pages for the same products, when you click page 2, only the additional products are fetched anew. All the balance data (including database data) on the page will remain constant.

- On clicking page 2, IE will keep non-database objects constant, but will fetch all database date anew

How does one implement browser side "query cache" in IE?