community postPlatform, DevOps & Performancecommunity - not Microsoftreviewed - checked by Opus

Dynamics 365 Business Central UI performance: what about the browser and the local machine?

Business Central UI performance depends on network latency, browser capabilities, and local machine hardware, not just backend optimization. The post explains how to measure and monitor these client-side factors during go-live and production.

post Stefano Demiliani

Stefano Demiliani · 2025-12-29 · 1,894 words · about 9 min

"Business Central is designed for networks that have a latency of 250 - 300 milliseconds (ms) or less."

Key points

  • Business Central is designed for browser-to-datacenter latency of 250 to 300 ms or less, and latency is the first thing to check
  • Use current stable Edge, Chrome or Safari; policies that block local storage or IndexedDB stop performance optimizations such as page caching
  • Each new browser tab reloads resources, takes around 10 seconds to open Business Central, and uses memory
  • CPU, RAM (16GB or more), GPU and SSD affect rendering speed; the author found recent Apple Silicon machines fastest
  • Page View telemetry, the Speedometer 3.1 benchmark and a Puppeteer-based Node.js script can help measure client performance, ideally on real hardware

Quotes

  • “Business Central is designed for networks that have a latency of 250 - 300 milliseconds (ms) or less.” (Establishes the key performance threshold for network latency that organizations must meet)

Context

  • Features: Page View telemetry, Page caching, WebSocket compression, IndexedDB database, Speedometer 3.1 benchmark, Puppeteer-based performance testing

Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.