Plugin abandoned but it is really fast. ONE PROBLEM with DOM access on scroll!

  • This rule counts the number of DOM-accessing functions calls on a scroll event, such as queries, readings, writings, bindings and jQuery functions.

    Two scroll events are triggered quickly, one after the other, and only the second one is analyzed so throttled functions are ignored.

    One of the main reasons of a poor scrolling experience is when too much JS is executed on each scroll event. Note that some devices such as smartphones and MacBooks send more scroll events than others.

    Reduce the number of DOM accesses inside scroll listeners. Put DOM queries outside them when possible. Use throttling or debouncing.
    =

    Warning

    This rule reached the abnormality threshold, which means there is a real problem you should care about.

    The table below shows the interactions between the JavaScript and the DOM on a scroll event.
    Type
    Params
    1
    documentScroll
    (triggering the scroll event on document)
    2
    windowScroll
    (triggering the scroll event on window)

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author nigro.simone

    (@nigrosimone)

    Plugin isn’t abbandoned.

    This plugin handle the scroll event anc check if the lazy image is into the screen. Use throttling or debouncing is a good suggestion. Thanks.

Viewing 1 replies (of 1 total)
  • The topic ‘Plugin abandoned but it is really fast. ONE PROBLEM with DOM access on scroll!’ is closed to new replies.