---
id: post/demiliani-com/13096
type: post
title: "Dynamics 365 Business Central UI performance: what about the browser and the local machine?"
summary: 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.
tier: community
language: en
tags:
  - performance
  - ui
  - browser
  - network latency
  - hardware
  - monitoring
  - diagnostics
  - optimization
system: platform
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:57:32.961Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: c19f670c5ee858ae6df28d07616af56c3a70293eac1d234c26b55c961d031a26
evidence:
  - kind: blog
    url: https://demiliani.com/2025/12/29/dynamics-365-business-central-ui-performance-what-about-the-browser-and-the-local-machine/
    title: "Dynamics 365 Business Central UI performance: what about the browser and the local machine?"
    date: "2025-12-29"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://demiliani.com/2025/12/29/dynamics-365-business-central-ui-performance-what-about-the-browser-and-the-local-machine/
    title: "Dynamics 365 Business Central UI performance: what about the browser and the local machine?"
    date: "2025-12-29"
    commit: null
    t: null
    quote: Business Central is designed for networks that have a latency of 250 - 300 milliseconds (ms) or less.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "13096"
source_id: demiliani-com
source_name: Stefano Demiliani
url: https://demiliani.com/2025/12/29/dynamics-365-business-central-ui-performance-what-about-the-browser-and-the-local-machine/
published_at: "2025-12-29T14:37:18.000Z"
author: Stefano Demiliani
full_text: false
words: 1894
quotes:
  - text: Business Central is designed for networks that have a latency of 250 - 300 milliseconds (ms) or less.
    why_it_matters: Establishes the key performance threshold for network latency that organizations must meet
code_objects_mentioned: []
systems:
  - platform
  - administration
versions_mentioned: []
preview:
  embeddable: true
  frame_url: https://demiliani.com/2025/12/29/dynamics-365-business-central-ui-performance-what-about-the-browser-and-the-local-machine/embed/
  image: https://i0.wp.com/demiliani.com/wp-content/uploads/2025/12/bcuislow_00.jpg?fit=1200%2C450&ssl=1
  image_alt: null
  image_w: 1200
  image_h: 450
  site_name: Stefano Demiliani
  favicon: https://demiliani.com/wp-content/uploads/2022/09/sd_wordpress_logo.png?w=32
  probed_at: "2026-10-07T11:51:11.489Z"
---

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

[Read the post](https://demiliani.com/2025/12/29/dynamics-365-business-central-ui-performance-what-about-the-browser-and-the-local-machine/) · Stefano Demiliani (Stefano Demiliani, MVP) · 2025-12-29 · 1894 words · tier community · reviewed (checked by Opus)

> 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.

## 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.