How can I find and solve the problem of Project page rendering efficiency (using the IE debugging tool probe)

# How did I find and solve the problem of Project page rendering efficiency (using the IE debugging tool probe)? There were a lot of registration pages in my project, generally, there are 100-200 or even more fields, and the display of dictionaries, dates, and other effects is also involved. loading is very slow and there will be stuck, in IE, I found a lot of information, but I still focused on the debugging tool provided by IE. At present, I used IE10 in my computer and IE9 in analysis, the ** probe ** page caught my attention. After a round of tossing, I learned the following analysis methods: 1. open the page for analysis, F12 enter the developer tool, and switch to the ** probe ** page 2. click Start sampling to perform a series of operations (because my problem is the efficiency of loading the page, it is natural to refresh the page), and then click this button again. if the view is switched to the 'call tree', the most time-consuming function call will be clear at a glance! [Probe] (http://images.cnitblog.com/blog/84053/201402/081733408821679.jpg) with this method to analyze the [demo page] (http://p2227.github.io/demo/applyLayout/elayout.html), the results of the layers of expansion (stripping), finally found the culprit :! [Time-consuming function] (http://images.cnitblog.com/blog/84053/201402/081740283894518.jpg) was originally the time-consuming easyui drop-down box, date box and layout component. You can solve the problem accordingly. So after a flip adjustment, re-define the page and HTML structure, so that the efficiency has been greatly improved [after the adjustment of the page] (http://p2227.github.io/demo/applyLayout/playout.html )! [Efficiency after adjustment] (http://images.cnitblog.com/blog/84053/201402/081755503737248.jpg) The details of the adjustment process will be sorted out later