1

I am using Dojo JS libraries in my project. The application runs on IE 6/7/8 and FireFox.

The application is working with a normal response time in IE7 and above and Firefox.

My Problem is

*When i run the application in IE6 , the page gets loaded very slow (takes upto 2 minutes).

I get errors like this :-

could not load dijit.form.button or could not load dijit.editor last tried ../Editor.js

But for the subsequent refreshes it works normally. Is this behavior because , the IE6 takes time to download the dojo scripts initially and for the next time it uses them from the cache.

Thanks! Pratik

Improve this question
4
  • Can you point to a demo page? Are you hosting the dojo libraries on your own server, or using one of the CDN options?
    – Sean Hogan
    Commented Feb 9, 2010 at 8:54
  • We are hosting the Dojo libraries on our own server
    – Pratik Garg
    Commented Feb 9, 2010 at 9:02
  • It's hard to diagnose without seeing the code, but you should try posting the exact error message you're seeing. Also, you should ultimately be running with an optimized 'build' for best performance, but that's unrelated to your current problem. Have you tried authoring a simple page with a widget to make sure it loads properly, then compare?
    – peller
    Commented Feb 9, 2010 at 21:51
  • 1
    There are many "______ is slow in IE6" questions, and they all have one thing in common...
    – Joel Mueller
    Commented Feb 11, 2010 at 22:17

1 Answer 1

Reset to default
4

I've also experienced this. Internet Explorer 6 has a much slower JavaScript interpreter than other modern browsers, which we can't change.

I think your first-load hit is caused by fresh requests for all of the source files as the Dojo parser bootstraps.

As Peller stated, a custom build script, containing source for only the objects you need can reduce the number of network requests needed to bootstrap Dojo.

This alleviated some of our performance issues, but even on subsequent refreshes we noticed IE6 taking substantially longer than IE7+, FF, Chrome, etc. to render the widget controls.

To try to reduce this, you can try to refactor large pages with many widgets into multiple smaller pages with fewer widgets. Can you convert any large monolithic forms into smaller step-by-step wizards?

You can try to encourage your users to upgrade to a newer browser.

Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.