Skip to main content
Question

Acumatica Dashboard : Reducing simultaneous widget requests on dashboard load (connection queuing)

  • July 29, 2026
  • 1 reply
  • 32 views

Hi All,

I have a dashboard with 20 widgets. It's causing the dashboard to load slowly (approx 30 secs).

We have already done SQL optimizations on the GIs, and also added Refresh Widget intervals — this helps with caching on repeat loads, but not the initial load.

Our remaining bottleneck is browser connection queuing: all ~20 widgets fire simultaneously on page load, and since browsers cap concurrent connections per host, later widgets queue behind earlier ones — this accounted for more total load time than the SQL cost did.

Also aware that Acumatica suggests a max of 10 widgets per dashboard, but this isn't a hard stop.

Questions:

  1. Does Acumatica's Dashboard framework support lazy-loading widgets (only fetching data when scrolled into view), a "load on demand" setting (as opposed to loading everything on page open), or parallel/staggered loading?
  2. Is there a supported way to stagger initial widget load requests on page render, rather than all firing at once?

Or any other way to help make the dashboard's initial load faster?

1 reply

Forum|alt.badge.img+4
  • Jr Varsity II
  • July 29, 2026

Hi ​@Halarnkar ,

According to my knowledge-

What the framework supports
Refresh Interval (which you already use) — helps on subsequent loads via caching, not initial.
"Load on Demand" / Lazy-loading — Not supported. The dashboard framework does not have a built-in mechanism to defer widget data loading until scroll or visibility. All widgets fire their data requests on page open.
Staggered/sequential loading — Not natively supported. There's no configuration to serialize or batch widget requests.
Practical options to reduce initial load time
1. Reduce widget count per dashboard — Split into multiple dashboards or use tabbed dashboard pages (multiple dashboard instances on Wiki tabs). This is the most effective fix.
2. Use fewer data-heavy widget types — Replace GI-based widgets with KPI or simple counter widgets where possible. Charts/grids with large result sets are the most expensive.
3. Consolidate GIs — If multiple widgets query similar data, consolidate into one GI powering a single widget with multiple columns/metrics rather than N separate widgets each hitting the DB.

Hope above helps!!