review-latency

To find blocking work in AutoHotkey scripts, audit latency-critical paths by analyzing window change to store updates and user input to pixel rendering for micro-optimization opportunities. This targets sub-millisecond responsiveness.

Frequent focus event lag occurs when minuscule delays in window eligibility checks compound during operations. Auditing the window change to store update path identifies these redundant computations and micro-optimization opportunities.

Profile AutoHotkey code for sub-millisecond responsiveness by auditing two primary hot paths: window change to store updates and user action to pixel rendering, targeting blocking work and redundant computation.

This performance audit specifically analyzes AutoHotkey scripts within the Alt-Tabby application's `src/core/` and `src/gui/` directories, focusing on its unique window switching latency paths and store update mechanisms.

The best way to optimize window change to store update paths is conducting a deep performance audit that targets blocking work, redundant computations, and micro-optimization opportunities to achieve sub-millisecond responsiveness.

Micro-optimization on AutoHotkey hot paths is unnecessary if the application already achieves sub-millisecond responsiveness or if the window change and user input paths lack measurable blocking work or redundant computation.