Hello Everyone
I am currently working on a web map that has around 180ish layers in it which is split across 3 ArcGIS server rest web services. These are all read only I have built the web map around 2/3 so far, I am noticing that the load time for two simple boundary layers that we have on by default is taking at least 10-15 seconds.
After looking in Chrome network activity the issues appear to be that the web map is making calls to all the endpoints when first loading which delays the overall map loading quickly seeing as only two small layers are on. In the old map viewer these layers load very quickly and don’t have the delay on them. I understand this is down to how the map viewers work etc.
I accept that a large number of layers will have a longer load time.
I am looking at this with ESRI support at the moment, we have scaling etc on layers so everything it restricted properly
I was wondering how you all deal with large web maps and how they behave in experience builder as I find they really struggle in experience builder
Can the break out this 1 web app into multiple web apps that have a smaller number of layers related to the topic of the individual web app (Not sure this is possible due to your business requirements, but just a suggestion)?
Wrote a response on this question that was posted.