Optimal strategy for Experience Builder with many widgets and data

Nadia_Matsiuk — Tue, 14 Oct 2025 12:57:01 GMT

Hi everyone,

I’m working with Experience Builder Developer Edition and have developed an interface that includes:

static cards with dynamic text,
a map with object information and a legend,
multiple charts of different types (around 12–15),
a filter widget for all of these.

Problem: the page loads very slowly.

I’ve investigated:
Using developer tools, I see the page sends almost 1000 requests, with 200 requests going to my ArcGIS Server. I analyzed these requests in detail: most are querying my data source, fetching fields and performing calculations for the widgets.

I’ve tried some optimizations:

creating views with only the necessary fields,
including only layers and tables that are actually used,
indexing the database.

These measures helped a bit, but the page is still extremely slow.

I’m looking for a comprehensive strategy:

How should such pages be designed in Experience Builder when there are many widgets and charts?

How to plan the server-side architecture, load balancer, and database setup?

Is Experience Builder suitable at all for pages of this complexity?

I would really appreciate detailed recommendations and best practices, especially from Esri developers🌎💛

Re: Optimal strategy for Experience Builder with many widgets and data

Wei_Ying — Mon, 17 Nov 2025 19:39:38 GMT

Thanks @Nadia_Matsiuk for your feedback.
How many charts are you having in a single page?

topic Optimal strategy for Experience Builder with many widgets and data in ArcGIS Experience Builder Questions

Optimal strategy for Experience Builder with many widgets and data

Re: Optimal strategy for Experience Builder with many widgets and data