We ran a "Multivariate Split Testing" for a client when assessing their User Experience to tune it better. We got around a hundred responses, and one of the most commonly sighted issue from the Testing Results was "Bad Scrolling Experience when Fullscreen Rows had been activated".
We saw how first time visitors interacted with the site as a part of our study as the client had requested for a report. First time users almost always had a messy experience with the scrolling of Fullscreen Rows. They would want to scroll down, and it just wouldn't react in the way they'd have wanted. The same was when the users wanted to scroll back up, it would take too much effort as the users would have to scroll once, wait for the animation (fast) to get done, then give the next scroll input, wait again, then give again etc. If they gave say two scroll inputs at the same time, only one Row would slide. Even though we had Row Anchors activated, from our study only 3% of First time users actually used it.
Second time users were more likely to get used to scrolling in Fullscreen Rows, by using less "wasted scrolls/swipes", but in their final feedback, around 63% still wrote comments about issues they faced with Fullscreen Rows.
We thought of not using Fullscreen Rows, but the client wants it.
Since our Test had almost 100 user feedback, I do think it is a major issue when it comes to User Experience.
Some users (22% of users) also suggested placing arrows on the page to help users navigate up or down, and another common suggestion (17% of users) was to have a back-to-top arrow appear on the Final Row. Another suggestion (15%) was to have the Arrows above and below the Row Anchors, and to somehow make the Anchors more visible as most of the First time users had missed it completely.
Hey!
We ran a "Multivariate Split Testing" for a client when assessing their User Experience to tune it better.
We got around a hundred responses, and one of the most commonly sighted issue from the Testing Results was "Bad Scrolling Experience when Fullscreen Rows had been activated".
We saw how first time visitors interacted with the site as a part of our study as the client had requested for a report. First time users almost always had a messy experience with the scrolling of Fullscreen Rows. They would want to scroll down, and it just wouldn't react in the way they'd have wanted. The same was when the users wanted to scroll back up, it would take too much effort as the users would have to scroll once, wait for the animation (fast) to get done, then give the next scroll input, wait again, then give again etc. If they gave say two scroll inputs at the same time, only one Row would slide. Even though we had Row Anchors activated, from our study only 3% of First time users actually used it.
Second time users were more likely to get used to scrolling in Fullscreen Rows, by using less "wasted scrolls/swipes", but in their final feedback, around 63% still wrote comments about issues they faced with Fullscreen Rows.
We thought of not using Fullscreen Rows, but the client wants it.
Since our Test had almost 100 user feedback, I do think it is a major issue when it comes to User Experience.
Some users (22% of users) also suggested placing arrows on the page to help users navigate up or down, and another common suggestion (17% of users) was to have a back-to-top arrow appear on the Final Row. Another suggestion (15%) was to have the Arrows above and below the Row Anchors, and to somehow make the Anchors more visible as most of the First time users had missed it completely.
Here are some other implementations that you guys could refer to:
1) https://alvarotrigo.com/fullPage/examples/continuous.html
2) https://www.cssscript.com/lightweight-full-page-scroll-pure-javascript-fullpage-js/
3) https://www.jqueryscript.net/layout/jQuery-Plugin-For-Fullscreen-One-Page-Scrolling-Websites-fullPage-js.html
4) https://webdevtrick.com/javascript-full-page-scrolling/
5) https://alvarotrigo.com/fullPage/#page2
6) https://alvarotrigo.com/fullPage/examples/apple.html
We did not run any tests on the above implementations, we only ran the test on Salient's implementation.
Alvarotrigo's "fullPage.js" seems to deal with scrolls much better.
We have gotten a lot more insights from this study, and we will share them as we properly document them by extracting the user data.
We hope you guys make the most of our study in further improving Salient!
Thanks!