Interaction latency measures the time between a user action and the software’s visual feedback. Delays above 100ms feel noticeably slow; mouse responses should target about 60ms and keyboard input about 50ms. section 3.2.4
Poor latency commonly develops when synchronous file operations run on the main thread, event handlers perform heavy computation, or UI frameworks batch updates inefficiently. Measure complete user flows rather than relying on vague goals such as “make it faster.” section 3.2.4 section 3.6
Use interaction latency as an operational performance target:
- Track the interval from user action to visual feedback. section 3.2.4
- Target mouse responses within 60ms and keyboard feedback within 50ms. section 3.2.4
- Use field data to discover user problems, lab data to debug them, and field data again to confirm impact. section 3.6
- Embed the target in the definition of done and revisit it as the product matures. section 3.6
Table 3.5 Desktop performance metrics
|
Metric
|
Measures
|
Example
|
|
Launch time
|
Time from click to first interactive screen
|
Application opens and shows content within 3s
|
|
Input latency
|
Delay between user action and visual feedback
|
Keystroke reflected on screen within 50ms
|
|
Resource consumption
|
CPU and memory usage during idle and active use
|
App uses under 1% CPU when idle
|
|
File operation time
|
Time to open, save, or sync files
|
50MB file opens within 3s
|
Compare input latency with launch time, resource consumption, and file operation time as complementary desktop performance metrics. section 3.2.4











