On the Skechers website,
Posted: Sun Dec 22, 2024 9:01 am
• JavaScript Events
The way JavaScript events work on most touch devices makes it impossible to implement lazy loading. JavaScript events are only fired when the user stops scrolling. Therefore, products cannot be added while scrolling: they will only appear when scrolling stops.
For these reasons, for mobile devices, our web design studio recommends loading only 15-30 products (until the “Load More” button appears). Then you just need to load the next set of 15-30 items (not “lazy loading”).
Key detail: the back button is supported via history.pushState
Over 7 years of usability testing, we have constantly seen how the technical implementation of loading a new page does not match the expectations of online store users, especially in the presence of dynamically loaded content such as overlays, accordions, filters and AJAX-loaded products.
studio-web-design
Using the “Load More” button requires a clear understanding of how the “Back” button works. It is important that when you click it on the page of a specific product from the list, the user returns to the point from which he went to the product page. Of all the online stores that used the “Load More” button, more than 90% did not work this way. This led to the user jumping back and forth through the product list and irrationally using the site navigation.
the system rewrites the URL every time a user uses the “Load More” button. Therefore, when a user clicks the back button from a product page, they are returned to the correct place in the product list.
The HTML5 History API allows you to set this up correctly. The history.pushState() function allows you to rewrite the URL without reloading the page, so the “Back” button will function correctly.
The browser will remember the position of the slider on the scroll japan whatsapp number list bar, but you need to make sure that when the user returns to the product list, all clicks on the “Load More” button will load by default.
Please note: If you do not have the technical resources to support the appropriate settings for the "Back" button, we recommend that you do not experiment with the "Load More" button and stick to the pagination method.
The "Load More" button shouldn't be a priority
While the debate over the benefits of using a Load More button/infinite scroll/pagination has been going on for years, the method of loading products should not be the absolute priority of your site's resource usage.
In recent years, more and more complex technical templates have appeared on online store websites. Many of them require significantly less technical resources than implementing a “Load More” button.
It is not that the loading method is not important. It is important, and during the study it became clear that it can significantly change the efficiency of working with the product list. If the site needs a number of changes and improvements, then changing the method of unloading products should not be an absolute priority. Thus, the “Load more” button is necessary for those sites that are only improving the user interface using their own resources or web studios.
So what should you choose?
To summarize , the research showed that the “Load More” button solved usability problems seen in pagination (where users viewed a smaller list of products and it was difficult to compare products across pages) and infinite scrolling (where users skimmed through products and often couldn’t reach the site’s footer).
However, the button only works effectively if the back button is implemented correctly (e.g. via history.pushState()), and when the solution is consistent with the context of use. As a web design studio, we have identified three key contextual settings for the component:
• Use a combination of the Load More button and lazy loading to navigate through categories. Set the Load More button threshold to 50-100 items.
• For search results, use the “Load More” button, but set the threshold to 25-75 items. Ideally, you should dynamically adjust the threshold for each unique search result list based on the relevance of the results.
• For mobile, use the “Load More” button, but set the threshold to 15-30 products, due to the complexity of scrolling and screen size. Also, due to JavaScript requirements and the lowered loading threshold, you should load all products at once, rather than using “lazy loading”.
If you liked our article, share it with your friends!
The way JavaScript events work on most touch devices makes it impossible to implement lazy loading. JavaScript events are only fired when the user stops scrolling. Therefore, products cannot be added while scrolling: they will only appear when scrolling stops.
For these reasons, for mobile devices, our web design studio recommends loading only 15-30 products (until the “Load More” button appears). Then you just need to load the next set of 15-30 items (not “lazy loading”).
Key detail: the back button is supported via history.pushState
Over 7 years of usability testing, we have constantly seen how the technical implementation of loading a new page does not match the expectations of online store users, especially in the presence of dynamically loaded content such as overlays, accordions, filters and AJAX-loaded products.
studio-web-design
Using the “Load More” button requires a clear understanding of how the “Back” button works. It is important that when you click it on the page of a specific product from the list, the user returns to the point from which he went to the product page. Of all the online stores that used the “Load More” button, more than 90% did not work this way. This led to the user jumping back and forth through the product list and irrationally using the site navigation.
the system rewrites the URL every time a user uses the “Load More” button. Therefore, when a user clicks the back button from a product page, they are returned to the correct place in the product list.
The HTML5 History API allows you to set this up correctly. The history.pushState() function allows you to rewrite the URL without reloading the page, so the “Back” button will function correctly.
The browser will remember the position of the slider on the scroll japan whatsapp number list bar, but you need to make sure that when the user returns to the product list, all clicks on the “Load More” button will load by default.
Please note: If you do not have the technical resources to support the appropriate settings for the "Back" button, we recommend that you do not experiment with the "Load More" button and stick to the pagination method.
The "Load More" button shouldn't be a priority
While the debate over the benefits of using a Load More button/infinite scroll/pagination has been going on for years, the method of loading products should not be the absolute priority of your site's resource usage.
In recent years, more and more complex technical templates have appeared on online store websites. Many of them require significantly less technical resources than implementing a “Load More” button.
It is not that the loading method is not important. It is important, and during the study it became clear that it can significantly change the efficiency of working with the product list. If the site needs a number of changes and improvements, then changing the method of unloading products should not be an absolute priority. Thus, the “Load more” button is necessary for those sites that are only improving the user interface using their own resources or web studios.
So what should you choose?
To summarize , the research showed that the “Load More” button solved usability problems seen in pagination (where users viewed a smaller list of products and it was difficult to compare products across pages) and infinite scrolling (where users skimmed through products and often couldn’t reach the site’s footer).
However, the button only works effectively if the back button is implemented correctly (e.g. via history.pushState()), and when the solution is consistent with the context of use. As a web design studio, we have identified three key contextual settings for the component:
• Use a combination of the Load More button and lazy loading to navigate through categories. Set the Load More button threshold to 50-100 items.
• For search results, use the “Load More” button, but set the threshold to 25-75 items. Ideally, you should dynamically adjust the threshold for each unique search result list based on the relevance of the results.
• For mobile, use the “Load More” button, but set the threshold to 15-30 products, due to the complexity of scrolling and screen size. Also, due to JavaScript requirements and the lowered loading threshold, you should load all products at once, rather than using “lazy loading”.
If you liked our article, share it with your friends!