ASP.NET App Slower in Edge than IE

Not reproducible Issue #10546250


Jan 16, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

We have an ASP.NET application that seems to run way slower in Edge than in IE. Running a test using the Performance tool and counting the number of seconds, Edge seems to take a lot longer in styling. Chrome seems to be even a little faster than IE, not to mention Edge. See the attached files. Is there a reason for this? What can we do to improve its performance.

Thanks in advance.

Jose A. Ortega


2 attachments

Comments and activity


    seen this issue few times. i don’t know if this issue has to do with .appendChild method in jquery or not?? i guess if possible some one should resolve this in edge build 15 preview sooner.

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Brad E.”

  • Hi Edge Team,

    Am facing big performance issue after upgrading my app from ASP.NET4.0 (IE9) to ASP.NET(4.5.2) IE Edge. Page rendering is slow. It takes more time to complete the full rendering of the page. Please suggest/provide a fix to resolve the issue.

  • Microsoft Edge Team

    Changed Assigned To from “Brad E.” to “James M.”

    Changed Status to “Not reproducible”

  • Hello,

    Thank you for providing this information about the issue. We are unable to reproduce this problem in Edge with the information at hand. Please reopen this case when you can provide a sample webpage and possibly source code for our investigation.

    Best Wishes,
    The MS Edge Team

  • Hi James,

    Reg: Slowness of page rendering issue in my 4.5.2 web app, we are using infragistics controls (webhtmleditors(text area with toolbars)also, i was posted a question in infragistics forum . can you please refer this link .

    We have further investigated the initialization performance issue with IE11 (value submission time described above are almost certainly caused by the page reloading again after).

    Through profiling we have determined the root cause to the in the native offsetHeight used for height adjustments. My best guess is requesting this height causes IE11 to do an excessive amount of extra calculations and quite likely multiple re-renders, which might also explain the large amounts of memory reserved.

    The calculations done are however required to properly size the control and editable area, so those cannot be completely avoided and usually yield minimal difference in common scenarios. We might consider other options for determining the effective height of the parts of the editor, however I see reports for the equivalent

    Note: How to resolve offSetheight issue in IE11 browser.

You need to sign in to your Microsoft account to add a comment.

Sign in