I hate those websites that paint within one second and then it takes two seconds to load all the other assets. It seems bare minimum to me. Idk about you all but I would rather have it loaded in three seconds instead of me trying to scroll immediately and thinking my computer is going to crash from the low framerate.

  • 3
    The common wisdom is that users become exponentially more likely to abandon a page the longer it takes to load. The confidence intervals for bounce rate by load time improve dramatically if you give the user feedback that something is happening immediately.

    Your understanding of the mechanism increased your tolerance for its potential problems.
  • 1
    @SortOfTested While this is true, I still think a variety of certain audiences would subconsciously have a bad experience with progressive loading - especially younger generations.

    It's like...would you rather have a YouTube video load for five seconds and then be able to play the whole video, or have it load a bit in one second and then have to wait another second after 10 seconds of playing?
  • 1
    That's a bit mixed metaphpor as it crosses media types (hypertext v hypermedia). There tend to be different rules for both, however youtube videos follow the same strategy in that they convey a familiar baseline ui and indicate loading is occuring. They also load the chrome first, then the content, for both videos and comments.
  • 1
    @phat-lasagna well, statistics say that the majority prefer fast response inmost cases.

    As you say, there are edge cases where it might not apply but for a web shop for example they have measured a statistical increase in profit.

    Sure there might be users that would prefer another approach but, are they more or less likely to actually buy something ;)

    Sometimes you do mot need to please every one, just those that will reward you.

    And it’s not only load times.

    Mozilla has a long article (couldnot find it now) on response time vs user experience and faster is almost always better, until you reach a limit.

    For example, when clicking a button, you should draw the popup immediately while loading content in the background, once the user have received feedback that the button works you have a lot more time to render the rest before the user starts to question it.
  • 1
    @Voxera Ur definitely right that they should follow the stats, but idk there's a few out there that paint really fast but when they try to load all their bulky components at once, the whole page seems like it's unreponsive forever lol. But I definitely find that whole topic of UX vs Speed facisnating, especially with RAIL and stuff like that.
  • 0
    @SortOfTested Yeah ur right that's a bad metaphor lol. I love the idea of loading components progressively tho. I just still hate that lagginess that big sites give. I guess most users don't feel the same ¯\_(ツ)_/¯
  • 1
    @phat-lasagna A bad implementation does not invalidate the idea ;)

    If they had loaded it all at once you probably would have to wait half a minute :P

    And choosing to follow best practice is not a guarantee that you succeed :)
Add Comment