Hi Hisako Ito,

The performance issues occur more frequently when the CSS file is larger or more complex.

The script ie11CustomeProperties.js is required because that script converts all CSS variables into simple custom properties. These properties are supported by IE and are similar, but with a few limitations, to the standard CSS variables.

To improve performance you can remove the other scripts (impact: less compatibility with other widgets)

The scripts mandatory are:

• ie11CistomProperties
• OutSystemsUI

You can follow the step by step in this article on Medium:

https://medium.com/noesis-low-code-solutions/outsystems-reactive-and-ie-compatability-7ed5717170b2

I hope it helps, and feel free to share your experience after removing the other widgets.

Cheers,

Luís

Hi Luís-san,

We really appreciate your kind and quick reply, thank you so much.

After we confirmed your reply, our developer team tried to improve the render speed based on your information.
However, unfortunately, our developer team said that the render speed was not improved as much as they expected because there is a possibility that the design of their Reactive web app is so complex.

Therefore their team will consider choosing apps type as Traditional or Reactive again.
And yet, I would like to report that our problem was solved with your advice.

Thank you for your cooperation :)

Best regards,
Hisako Ito (BlueMeme Inc.)

Hi Hisako,

Another possible solution is redirecting your users from IE  to a webtradional application:

To achieve this you need to add the function IsInternetExplorer on the Initialize of your screen:

This solution's constraint is building two applications, the Reactive for the modern browsers and the IE in webTradional.

Cheers,

Luís

Also experiencing very slow render but on a reasonably simple reactive application