The ratio of interactions that enter text into text fields is relatively high in comparison with the other user interactions ( %). This should be reduced. As an example, entering data can also be done using check boxes or combo boxes in the case predefined values must be entered. In of times ( %) of entering text into text field , the same text was also entered into text field during the same session. Perhaps this can be automated, so that the user does not have to reenter the same text several times into different text fields. % of the text entered into text field was no letter or digit. This is an indicator that the entered data has to follow a specific syntax. This should be supported by syntax checking, auto completion or even providing the text fields in a way that does not require the entering of special signs as they are already included at the right positions. The task covers % of all recorded user actions. Therefore, it should be executed with a high efficiency. You should consider making the task more efficient, by minimizing the number of actions to be executed by users for fulfilling this task. For executing task , the user has to execute a high number of inefficient actions ( % in average). Such actions are, e.g., scrolls. The number of inefficient actions should be as minimal as possible to increase the users efficiency in executing a task. Please check the task structure for occurrences of the following event tasks and consider to prevent them: scrolling (usually prevented by matching the size of a view to the available screen space). In % of all occurrences, the task is succeeded by . This shows, that both tasks are likely used in combination. Please consider to support the execution of both tasks in one user action, e.g., by providing an appropriate button, to reduce the number of actions to be performed by the user. In % of all occurrences, the task is preceded by . This shows, that both tasks are likely used in combination. Please consider to support the execution of both tasks in one user action, e.g., by providing an appropriate button, to reduce the number of actions to be performed by the user. For executing the task , the user utilizes GUI elements on average. As these GUI elements have a high distance to each other ( on average ), they should be more colocated to ease the execution of the task for the user. A click on the button seems to be missing user feedback. In of uses, the button was clicked several times. The average waiting time between two subsequent clicks is seconds. This is typical user behavior if the user does not see progress following his actions. Please consider showing the user some progress after he performed the first click. This is especially important if the operation triggered with the click usually takes longer than one second. This smell was observed based on task . The task is often retried, i.e., repeated subsequently. On average, every th instance is followed by one or more repetitions of the task and the average repetition ratio when a task is repeated is additional repetitions. This can be task retries and may indicate, that the task is hard to be performed. Hence, it should be eased up. This can be done by checking, why the task is retried and then adapting the implementation so that the task can be finalized with its initial execution. In times the view is displayed, the following GUI elements belonging to the view were never used. They make up % of all interaction elements in that view. This indicates, that they are not required and can, therefore, be removed. The unused GUI elements are: When executing task , the users have to switch between keyboard and mouse in % on average between two subsequently executed actions. Frequently changing between mouse and keyboard causes users to become slow when utilizing a GUI. Hence, these should be minimized to optimize the users performance. When using GUI element in view , the values selected by the users are not equally distributed. Hence, it may be useful to have a good default value. The users entered the following values with their respective frequency in brackets most often (only the five most important entries listed): Found a group of check boxes of which only one is usually selected. In usages of the check box group, times ( %) only one of all check boxes was selected finally by the user (considering, that all check boxes are always unchecked when they are displayed). If the alternatives represented by the check boxes are mutually exclusive, radio buttons should be used instead. The check boxes belonging to the group are: The user sessions show only a few commonalities. On average, ten subsequently executed actions need to be described by different determined . In the worst case, each action is its own task. In the best case, all actions are described by the same tasks. This indicates, that the users act relatively different as otherwise, all their actions would be described by only a few tasks. Hence, users seem to be missing guidance, as otherwise, they would behave similar resulting in less generated task which still cover many recorded actions. In the times it has been displayed to users, the element has been clicked times although it may not be clickable (it is no, e.g., button). If the element is not clickable, then the element seems to give a cue that it was clickable although it is not. Hence, it should be considered to change the appearance of the element to prevent it from looking clickable. When opening the view , users most often position the cursor into the text field (in % of cases when the view is opened). This should be automated to remove one action required for users.