So much great work has been done of shopfront load time so I hope folks don’t read this and sigh!
Products Caching works well for most clients. But Stroudco have been finding that users with slower machines are failing to load the page. As a large part of our goal in the UK is to make real food accessible to people on low incomes it is inherently designed into our service that we are going to be working with people with old computers running old browsers.
Currently OFN loads the full product set before displaying the shopfront. For shops with 500+ products this means 500+ requests to our image server which seems to be the main time waster. We often hear complaints of Stroudco shopfront timing out on old browsers and Stroudco have seen a drop in sales that at least is partially related.
Much talk has gone on of pagination. In many ways this is not an ideal solution by itself. By not loading everything into the DOM at the start though we end up with searching needing to send a rq to the server. Sending these RQs to the cache will help but it seems there is a strong feeling to have the full product set loaded into the DOM from the start.
With this in mind @pmackay and I have discussed a number of options.
The most recent favourite would be a kind of pagination on the loading of images only. Paul suggested auto-scroll so that as the user scrolls down the next set of images loads. Image loading could potentially be done asynchronously in the background, but loaded as batches so as not to create a confusing user experience as the page jumps about as each image loads (I hate that).
Would be great to find out if this is possible? Practical? A potential good solution? Totally ridiculous?
@oeoeaio I ping you for your detailed knowledge of angular. It would be great to hear any quick initial thoughts on feasibility.
@RohanM I ping you to find out how this solution sits with you and all the work you’ve done on the cache.
@maikel I bet you have interesting things to contribute too