AI-based Issue Detection Engine
HeadSpin AI-based Issue Detection Engine
The HeadSpin AI automatically detects and provides actionable insight into the root causes of issues due to network, device, and app architecture performance.
Note that some issue analyses require permissions to run. If you have any questions about whether your org has the necessary permissions for certain issues, please contact your HeadSpin administrator for assistance.
Impact Time is HeadSpin's proprietary performance metric. It measures the amount of time a session is affected by an issue, taking into account our benchmark for app performance. Typically, the total Impact Time is the time added to the length of the session. If addressed, users can accomplish the session's tasks or User Flow in that much less time. Resolving high Impact Time issues will typically yield the biggest performance boosts.
Impact Time is measured relative to a benchmark. The benchmark for an issue is the expected amount of time for an optimized app to accomplish the same tasks. If a task is accomplished during a session in less time than the benchmark, the app is considered to have performed satisfactorily with respect to that issue. On the other hand, an Impact Time above 0 signifies poor performance relative to the benchmark, and represents an opportunity for performance improvement. HeadSpin will flag all such issues in the Waterfall and the Issue UI.
The Union Impact Time of a session provides an estimate of how much the session's specific User Flow can be improved. It is an aggregation of the Impact Time from all issues, merging any overlapping Impact Time regions regardless of how many issues affect them. The Union Impact Time is bounded by 0 and the duration of the session.
Types of Issues
HeadSpin distinguishes between four types of issues: user experience issues, root cause issues, warnings, and testing pitfalls.
User experience issues are issues as perceived from an end user's perspective. They describe the experience of the user when using the app. These issues do not provide immediate insights into the underlying cause or how to fix them. However, they suggest high visibility issues to investigate in order to improve the quality of the user experience.
Root cause issues are discovered through the monitoring of device and network status. These issues tell you exactly what went wrong in the session, and how to fix it.
Fixing root cause issues may also improve, though not necessary eliminate, the Impact Time for user experience issues.
Warnings are issues that do not incur any Impact Time but can still be improved. Warnings include security risks or tips on how to maximize the insights gained from the HeadSpin platform.
Pitfall issues are issues that do not affect real end users and are attributable to some suboptimal usage or configuration at the interface between your application and the HeadSpin Platform. These issues may adversely affect or prohibit the capture of certain data or require some action or trade-off to maximize the value of the data captured.