From my experience, a lot of the JS errors are not fatal but when it is impactful, it can ruin the whole experience. So, it is important to know the impact of JS errors on your users and fix them as we find them.
In Browsee, you can identify the commonly occuring JS Errors and see the related sessions to prioritize your JS Errors fixing.
While watching the session recordings, you will be able to locate via timestamp the exact location of your error. You do not even need to watch the complete session recording, you can directly jump to the point where the error has occurred.
If you realize that the error has no impact on the users or are benign, you can also mark those to be ignored in future sessions and Browsee will not record these errors in the future.
AJAX calls are quite commonly used for frontend development which updates a webpage without reloading the whole page. This is better as instead of the complete page only a part of the page gets updated. For example, your data tables are usually loaded with AJAX calls.
What happens when these AJAX calls are slow? It will hurt the user experience and if it takes too much time to load, users may leave without even waiting for the data to load!
It is important to understand the impact of slowness on your UX. Some calls are more important than others.
You can identify the impact of any AJAX slowness or errors via Browsee -
In Browsee, you exactly know which call took longer to respond, by watching the session you can see its impact on the UX and you can mark it resolved in case it is not impacting your UX.
Not only you can identify the impact of slow AJAX calls, you can also see the impact of any AJAX errors. Sometimes, the errors are benign. For example, if there is an error while sending data to your analytics server, it will not impact your UX. In those cases, you can mark them as resolved and we will not mark such sessions further.
For sanity, Browsee does not provide any errors or slowness related to 3rd party tools like GA, etc.
What is the most common behaviour of a user when a click does not work or is extremely slow in responding? Yes, you guessed it right - Rage or Frustration!
A common user behavior in such a scenario - Clicking multiple times on the same button or at the same element on the page.
Browsee tags all your sessions where a user was found to be clicking multiple times at a very small interval on the same element. This might happen in a session when -
A click is not responding
A click is too slow to respond
The element looks clickable but it is not
You can identify such sessions in Browsee by applying Frustration Click Filter -
Exactly know which element is getting the frustration clicks -
Looks like the signup button is not working! By watching sessions for frustration clicks, you can easily analyze if any of your buttons are not working or giving a slow response.