Autoptimize lazy load vs WordPress native lazy load

I was just wondering what the differences are between Autoptimize lazy load and the native WordPress lazy load?

I disabled lazy loading in Autoptimize after WordPress added this feature. Then I noticed that the native Wordperss lazy loading was not working for external images (images not hosted on my own site). So I enabled Autoptimize lazy loading again and everything was working fine, all images were lazy loaded.

Then I was using the EWWW plugin to serve .webp images using the <picture> tag method. This had some kind of conflict with Autoptimize lazy loading (I think the images were not loading at all iirc). So I had to disable Autoptimize lazy loading again.

Now I am serving .webp images using another method (NGINX conditional rules) so I have the option to enable Autoptimize lazy loading again. However, I noticed that it adds an additional javascript file which is not combined with the others.

I only have a few pages with external images, but those few pages have a very high number of external images. I’m not sure if it’s worth loading that extra js file on every page or not.

Are there any other differences between native lazy loading and Autoptimize lazy loading that I should be aware of? Does one work better than the other in different situations?