WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #44427, comment 15


Ignore:
Timestamp:
08/08/2019 12:32:29 PM (7 months ago)
Author:
JakePT
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #44427, comment 15

    initial v1  
    1010
    1111So my argument is that while lazy loading might help with bandwidth and memory usage, which is not meaningless, it is a considerably poorer user experience for anyone that is not on a high speed connection. As such I believe that any application of lazy loading needs to carefully consider which images it's used for, and that this is highly dependent on context and not a decision that WordPress should be making bluntly for all sites like this. If even Google believed that lazy loading was preferable for all (or even most) contexts, they would have made it the default browser behaviour for loading images. So why should WordPress make this behaviour the default? I believe that at ''most'' WordPress should add a checkbox for enabling lazy loading to the image insert/edit modals.
     12
     13Perhaps I've just had experience with poor implementations, but this just boils down to me really wanting to see more consideration of the user experience of lazy loading, as well as some articulation of what the performance benefits actually are if performance is the justification (and not bandwidth/memory usage).