I am using plain JavaScript for this part. In the first two methods I am cloning elements rather than creating them.
Method 3) create a text HTML representation and set the innerHTML. At the end insert the fragment into the DOM Method 2) create a document fragment and append into that. Method 1) create elements and insert directly into the DOM but that would be lots of = 'time: ' + (end - start) Reducing the number of SPFx webparts in the page is the only way to make it load faster in IE 11 ( it's a pile of hay :) ). While jQuery and moment JS can be replaced with some work, PnPJS & Knockout have to stay.Ģ - Bundling some of the small vendor JS files ( pubsub ) by taking them out from external.ģ - Loading dependencies once by master page and taking them out of SPFx project ( package.json & config.json ) while only leaving devDependencies ( to get TS to compile peacefully ) although the dependencies were either bundles with SPFx JS file or I was hit by this issue.
I have tested the following but didn't have much better performance in IE 11.ġ - Reducing the number of external dependencies ( taking out JQuery & moment JS and leaving PnPJS & Knockout ). Technically speaking, cached requests shouldn't be an issue, although the duplication of cached requests is the only difference I could see in Dev tool between IE 11 & Chrome Thanks is no single point of slowness but just too many small requests, it's like adding to a pile of hay. I have tried loading dependencies by master page and taking them out of SPFx project ( package.json & config.json ) while only leaving devDependencies ( to get TS to compile peacefully ) although the dependencies were either bundles with SPFx JS file or I was hit by this issue Unfortunately IE 11/Win 7 is the standard operating environment for my case and instructing users to use Chrome or Edge is not an option.
Internet explorer 11 slow windows 7#
Performance is worst in IE 11 on windows 7 compared to IE 11 on windows 10. I can see that all dependencies loaded multiple times in IE 11 dev tools while they are loaded once in Chrome dev toolsĪll JS dependencies for SPFx are included as externals The page contains 9 SPFx webparts and it produces 115 ajax calls and 163.73 page payload ( cached )
Internet explorer 11 slow how to#
Observed Behaviorġ - It is not possible to bundle SPFx js files for v1.1 ( on premise SharePoint 2016 ).Ģ - While it's possible to bundle Vendor JS files, but how to configure SPFx to load vendors JS files from common bundle rather than doing separate cached http request for each library. CategoryĪn easy way to improve SPFx page load in IE 11. While all modern browsers can handle that peacefully, IE 11 can't!įor a page with 6 SPFx webparts ( ideal home page with multiple tiles ) the resulting number of requests is around 40 ( mostly from browser cache ), again for all modern browsers this loads in less than 2 seconds but for IE11, it takes around 5 seconds, which is not acceptable. Internet Explorer 11 is still the standard operating environment for many companies which makes the pages with multiple SPFx webparts really slow.Įach SPFx webpart by design adds at least 4 cached http requests ( webpart bundle JS file + few other JS libraries like jQuery, Angular & PnP JS ) + Rest/CSOM API for the webpart logic.
0 kommentar(er)
