Internet Explorer navigation time

Edit Subject

Hello Jerry,

Naturally adding more logics to a process will add an overhead and thus more loading time.

As you mention, there is an overhead even when your code is empty due to our engine layer processes on top of the browser - of less than half a second.

This is a "reasonable" delay when running an abstraction layer on top of the browser that takes care of all the logics and functionalities in the background.

Having said that, we are constantly trying to reduce this overhead to make our framework even faster and striving to reduce this to the minimum to also be able to prevent the IE warning.

Thank you for your quick reply. I agree that this overhead is to be expected, but as long as explorer complains, it gives a badimpression to our users.

Looks like we'll have to find a different solution for explorer (what else is new? ;-) )

Jerry,

From our experience this IE message have little affect on your active users. (Meaning that your churn will probably not be affected by this)

In any case finding a new solution or framework would come with it's own overheads and I find it hard to believe that it will show better performance than Crossrider.

On top of this, it's worth mentioning that Crossrider as a framework has plenty of advantages, including our cloud-based auto-update mechanisms for both your extension code and the actual Crossrider engine.

Also with Crossrider, you get rid of all the headache of taking care of new version releases as we take care of all this for our developers, leaving them (and you) to focus only on their core product.

As I mentioned above, we will keep working on improving the overall performance of our framework so in the future, messages like these will be avoided altogether.

How did you make the test ?

I commented out all our own code until only this was left in extension.js and background.js:

appAPI.ready(function($) {
});

Then I re-installed the add-on in IE9 and browsed through 10 pages. After that I opened the "manage add-ons" window and noticed a navigation time of 0.4 seconds.