Loading and scroll

Loading and scroll behavior determine whether a long product list feels like one continuous task or a sequence of resets. The business outcome is preserved browsing progress across loading, product visits, Back, refresh, and device constraints.

This module covers how products enter the list, how much context remains visible, how URLs represent state, and how shoppers return to the same filters, page or loaded set, and position. These decisions belong together because scroll restoration is meaningless when the underlying list reloads differently. Baymard’s research documents the cost of returning shoppers to the top and covers pagination, load-more, and endless-scroll patterns.¹

Choose the loading model around catalog length, footer access, performance, accessibility, and restoration requirements. Then define the complete state that must survive navigation. Do not approve an endless list because it feels modern or pagination because it is familiar.

Module diagnostic

Use the longest important collection on desktop and mobile. Apply filters and sort, move beyond the initial product set, open a product, return with Back, reload, and share the URL in a new window. Record the loaded set, page, filters, sort, position, focus, footer access, and any duplicate or skipped products at every step.

Small assignment

Write a state-and-loading brief for the first broken journey. Name the loading model, URL fields, history behavior, restoration point, missing-product fallback, expiry rule, loading feedback, accessibility behavior, performance owner, and repeatable QA sequence.

Evidence and further reading

1. [1]“Return Users to the Same Place in the Product List When Returning from the Product Page,” Baymard Institute, https://baymard.com/blog/return-same-place. Supports restoring shoppers to their previous list position across common product-loading patterns. Accessed August 23, 2026.