Curious lazy loading results

  • Resolved cag8f

    (@cag8f)


    5 years, 9 months ago

    Hello. I have question about your lazy loading functionality. Your documentations says,

    >> When JavaScript then loads, it will look for all images in the current view and replace the src attribute with what is in data-lazy-src. This also occurs as the user scrolls down the page and images come into view.

    So I understand that when a user loads the page, images below the current view will be not be loaded–they will be loaded as they come into view. But what about images that are already in the current view, but currently hidden? For example, my page displays an image slider at the very top of the page. The slider contains five images, but only one is visible at any time. So will your lazy load feature ensure that, on page load, only the first image is loaded, with the remaining four images loaded one at a time, only it comes time to display that particular slide?

    To test, I’ve used Google’s PageSpeed insights. I’m getting some curious results. For its test of my mobile site, it reports that zero of the five slider images are lazy loading (screenshot). For its test of my desktop site, it reports that all slider images except one are lazy loading (screenshot). But I would expect this lone non-lazy load image to be the slider image that is displayed on page load, but it not–it is the second image in the this one image is *not* the image. Any explanations for these results? Why there is a discrepancy between desktop and mobile? And why does neither test return the expected lazy loaded images?

    Thanks.

    • This topic was modified 5 years, 9 months ago by cag8f.

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

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi there,

    Right now, I’m seeing an error in your site’s connection to Jetpack, which could be causing these intermittent issues with the Lazy Loading module.

    While your site is publicly accessible, we cannot access your site’s XML-RPC file. I would recommend that you check the following:

    1. Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.

    2. Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

    Once we are able to access your site’s xmlrpc.php file, that may clear this odd behavior you’re seeing.

    Let us know how that goes ??

    Thread Starter cag8f

    (@cag8f)

    OK thanks for the reply.

    >> Do you use any security plugins that may block access to this file?

    I do indeed have the Wordfence security pluin installed and activated, with the default settings. In my .htaccess I see the following code:

    <Files xmlrpc.php>
order deny,allow
deny from all
allow from 123.123.123.123
</Files>

    Would this be the culprit? It is unclear whether that specific code is from Wordfence or not. I can inquire, or perhaps temporarily disable Wordfence to test. Alternatively, I have a private dev site. I could deactivate Wordfence on the dev site so we could re-run the same tests. Maybe that would be best? Let me know.

    >> Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

    I can do this, but let’s investigate Wordfence first, since it is the more probable suspect, and the lower hanging of the fruit.

    Thanks.

    Plugin Support Fotis

    (@fstat)

    Hi there,

    Actually, you can test your site in the Jetpack debugger yourself:

    https://jetpack.com/support/debug/

    Disable the Wordfence plugin, run the site through the debugger, and let us know of the results.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Curious lazy loading results’ is closed to new replies.