One of our major goals this year is to expand the NoibuJS script’s capabilities beyond capturing JavaScript and HTTP errors. By tracking a wider range of error types, Noibu gives you the greatest insight possible into the health of your eCommerce site. Earlier this year, we added GQL errors to our roster of error types, and we’re pleased to announce yet another impactful addition: Content Loading Errors.
A content loading error occurs when images are not properly loaded, and results in a webpage not displaying as intended. A broken image or styling element usually won’t directly block a client from advancing through the checkout, so most content loading issues are assigned $0 ARL. However, any disruption to the user experience can breed friction and may affect conversion rates. It’s especially problematic if a content loading issue affects product images, as few shoppers will buy a product they can’t preview.
Content loading errors are identified as IMG in the Type column in the Issue table, and will only appear on the All Issues tab. We’ve also added filtering options for both new error types. Open the filter and expand the Error Type menu to filter the table by HTTP, JS, GQL, or Image errors.
For now, Noibu will only capture issues with image files, but we hope to expand this functionality in the near future to include script and CSS issues.
Additionally, Noibu will only report a content loading error if we detect a minimum threshold of sessions affected. This prevents one-time issues from spamming the Issues table. We'll be experimenting with this threshold in the coming months to produce the best results.