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 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
.
% of the GUI elements (
of
) are not used. This can have several reasons. Either they are not
visible to the user or they are not required. If they are important, they may not be
recognized by the user. This can be caused by visual design or because they are too hidden.
If they are less important, they can either be removed from the GUI or relocated to a less
prominent position. 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 this case, radio
buttons should be used instead, if the alternatives are mutually exclusive. 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 tasks. 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 the view
has been displayed, 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.