Right now, it is challenging to track delays induced by bad network behavior or bad client systems for the F&O web client, specifically:

• Latency on the network level
• Latency due to browser rendering
• Memory pressure on the client
• CPU pressure on the client
• Timeouts on connections
• Network connection type (wired, wireless, with or without VPN)

There are possibly more ideas on client telemetry, the WHS mobile app telemetry is a great example of this. It would make debugging potentially slow clients much more apparent. In the past, we had several instances of random performance issues, which turned out to be bad clients or networking.