Loupsio finds what blocks your customers.
In every visit, Loupsio looks for what gets stuck: a button that doesn’t respond, an error, a refused field, a page that is too slow. It groups the visits that share a problem and puts the one affecting the most sessions at the top of the list.
The signals Loupsio looks for
Detection works from the first recorded visit. You don’t have to add tags or declare events.
Repeated clicks
The visitor clicks the same element several times in a row, often because the button doesn’t respond or responds too slowly.
Dead clicks
The visitor clicks an image, some text or a button, and nothing changes on the page.
JavaScript errors
Loupsio keeps the exact message and the page. An error that repeats on the same page counts once, with its number of repeats.
Refused fields
The form refuses an entry, a postcode or a phone number for example. Loupsio says which field, without ever reading what was typed.
Quick backs and frantic scrolling
The visitor leaves a page right away, or scrolls it up and down without stopping: they can’t find what they came for.
Slow pages
A page takes more than 4 seconds to show its main content on the visitor’s device.
Send the problem to whoever fixes it
You choose who fixes it, then send them a link with the page, the element, the number of visits affected and a replay. They can open it without a Loupsio account.
- Your developer, your agency, the marketing team or the content team
- Loupsio opens your mail app with the message already written, or creates a Jira, Linear or Trello ticket
- The link expires after a set time
Check that the fix worked
When you mark a friction as fixed, Loupsio compares the share of affected visits before and after. It gives its verdict after 7 days and at least 50 visits to the page, and the result shows up in the Monday report.
- The verdict: confirmed, no effect or to be confirmed
- What each friction costs in lost sales per week, as soon as Loupsio knows order amounts (Shopify pixel or one line of code)
- You can ignore frictions that don’t concern you
- Frictions that appeared during the period are marked as new
Frequently asked questions
Do I need to set anything up?
No. Once the script is installed, detection works on every page.
What if page text is masked?
The friction then takes the element’s name, for example button#apply, instead of its text.
What about problems that happen only once?
Frictions are grouped by element and page, then ranked by number of sessions affected. A one-off problem stays at the bottom of the list.