This is a migrated thread and some comments may be shown as answers.

Slow performance in IE browser when loading a page with nested radsplitter

1 Answer 7 Views
Splitter
This is a migrated thread and some comments may be shown as answers.
JC
Top achievements
Rank 1
JC asked on 02 Nov 2016, 02:02 PM

Hi,
the project, in which I’m working, have a performance issue in IE, when the page is loading in IE11, it takes between 2.5-4.5 seconds, while in chrome it takes less than a second to load (firefox/Edge load in less than 2 seconds);  Resize is also a problem, but my main concern is Loading the pages… the master page has multiple nested splitters (rad panes), I debug it and server’s time is less than a second, using dynatrace, fiddler, and dev tools, I find that the time is related to the Resizing of panes…
(See images  https://screenshot.net/7o1dgcn  ,   https://screenshot.net/jd9qgud )
I’ve looked at multiple forums (both telerik’s and otanother sources) for similar problems, and optimizing tricks… I tried some of them, but the resizing is still the main issue...
I include a link to a video showing the problem http://screencast.com/t/LQNCaVFD (ie vs chrome) with a simple project, one with one single radsplitter (RadPanelSingleSplitter.aspx) the other one with multiple nested radsplitters (RadPanelNesting.aspx, which is similar to my project), the nesting page takes at least double the time to load, and also the more html I include, the more time it takes to render (resize)…

Has anyone else have similar issues?

Best Regards,
JC 

1 Answer, 1 is accepted

Sort by
0
Vessy
Telerik team
answered on 03 Nov 2016, 03:48 PM
Hi JC,

I have just answered your support ticket on the matter - please, refer my comment there.

On a side note, I would like to mention that posting multiple tickets on the same topic will not assure you a faster response. In future cases of help needed, please make sure to keep the information in one thread so  that it can be handled by the support engineer and consider all the information data provided. Scattering the same topic into several threads may cause information loss and even slower down our response time as wee will have to address multiple threads instead of one.

Regards,
Vessy
Telerik by Progress
Check out the new UI for ASP.NET Core, the most complete UI suite for ASP.NET Core development on the market, with 60+ tried-and-tested widgets, based on Kendo UI.
Tags
Splitter
Asked by
JC
Top achievements
Rank 1
Answers by
Vessy
Telerik team
Share this question
or