I have looked around at other types of lazyload and all of them allows the option to define a specific image class to apply lazyload for, allowing control for where lazyload should only be applied.
But the JA Lazyload plugin searches the body for all <img> tags and replaces them with lazyload code. By default, there is no problem with such implementation but when attempting to use plugins / modules that manipulate the way images are displayed like slider or gallery, lazyload becomes very annoying.
This afternoon it pissed me off when the gallery keep picking up lazyload’s cache png and so I decided to kill lazyload on item view with a single line of code.
Open jalazyload.php and look for this line
if ($app->isAdmin()) return;
Below that line, add this new line
if(JRequest::getVar("view") == "item") return false;
Now lazyload will be killed when on item view (the article page). But it will still work on the frontpage and category pages which is where we really need lazyload, else next page won’t load until all intro images are fully loaded. Lazyload solves that issue, allowing almost instant page load.
Actually killing lazyload on item view also helps to allow search engines to index images on your article page, so there’s only pros and no cons to this approach. Hopefully Joomlart can implement an Yes/No option in future versions of the plugin to disable lazyload on item view.