Thread

Hello There,

First-time EE builder/poster here. My site† is loading smoothly in Chrome, FF,and Safari. However, when in IE it tends to hang* for a couple seconds. It is compatible with IE in all other respects. I have gone through plenty of optimization techniques and have not had any lucking finding a bottleneck or obvious issues in my troubleshooting.

I’m wondering if anyone can provide additional insight as to what could cause something like this to only happen in IE.

Cheers,
Daniel

† using EE Version: 2.1.3 - Build: 20101220 with Structure and a few other plugins

* it totally freezes the browser just before completing the loading process

Hi Daniel,

Welcome to the forums!

Which version of IE is displaying this issue? Is this only in the CP or the frontend or both?

Cheers

Greg

Hey Greg,

Thanks for responding. It seems to be happening in all versions of IE (haven’t tested it in 9 beta yet) and is only the frontend that has this loading issue.

VitaminsGood, you may want to try turning off Generate HTTP Headers, in Admin>Content Administration>Output and Debugging Preferences, and see if your IE delay problems go away.

This is not an exact fit for issues which have occurred before, but it kind of feels worth the try, given how simple it is to do.

Let us know your results, please, as it could bear on other conversations.

Regards,
Clive

Turning off Generate HTTP Headers made no difference.

Ok, VitaminsGood, and your test at least helps the community on another issue.

I don’t know what further to suggest as far as IE time issues from EE. My own site sees snappy ie8 response, for example; not different from other browsers, and I haven’t heard any other issues with IE from ExpressionEngine.

For this reason, I would look particularly at your HTML, JavaScript, and CSS page design, particularly since all IE browsers seem upset.

It would be nice if there were better debugging facilities for IE. What you might try in lieu of them is making a copy of your template under a different name, and simplifying by leaving out larger or smaller parts of it, until you find what isn’t loading and displaying quickly. Then there will be a clue, or an answer.

Stock advice, I know—but best idea that comes this morning anyway.

Regards,
Clive

Daniel,

Have you got a link to the page in question we could have a look at please?

Great News. The loading issue has been resolved and was being caused by an IE filter property in a CSS file for a JS plugin.

Thanks for the advice.

VitaminIsGood, very good to hear.

Glad you found it.

Regards,
Clive

Excellent. Please post again as needed.