Dashboard indicators slow to respond

[JoshuaMcLemore]

Hello everyone, we have a dashboard that is configured to show various data points regarding new subdivisions that get approved and get built out over time. The issue we are facing currently is how slow the dashboard responds when you interact with it. Is this a common challenge with dashboard and or what are other ways to work around this to improve the user experience and improve the reaction of the Dashboard. 

[jcarlson]

It's really going to depend on where the data is coming from. Can you describe the underlying data a bit more? Is it a hosted layer, or a registered ArcGIS Server layer? Map Server vs Feature Server? How many sub-layers, how many features in each?

We don't have any issues with our dashboards, so it's probably something to do with your specific setup. Any chance the dashboard is public? Can you link to it?

[JoshuaMcLemore]

https://pcsb.maps.arcgis.com/apps/dashboards/d5e60365a9a04cb798e18c956a2af5d5 

[ArielLow2146]

Several suggestions:

1. Your layer is publicly editable. This is strongly recommended against for performant public data display.
2. It seems like your Concurrency and Development Tracking layer is on when the map loads. Given the number of features in the layer it would be good to set a visibility range and only have it load when the user zooms in.
3. If you'd like to see the layer at a small scale it would be good to optimize layer drawing. https://doc.arcgis.com/en/arcgis-online/manage-data/manage-hosted-feature-layers.htm#ESRI_SECTION1_7...
4. I'd also set up attribute indexes on any of the fields you've set up indicators against. https://doc.arcgis.com/en/arcgis-online/manage-data/manage-hosted-feature-layers.htm#ESRI_SECTION1_0...
5. If you've republished the layer or edited the data it wouldn't hurt to rebuild the spatial index.
6. I'd make sure the caching interval is set to as long as possible. https://doc.arcgis.com/en/arcgis-online/manage-data/control-cache.htm
7. I'd limit the number of list results returned.