Yeah, it's one of those lazy loading js implementations that tries to be too clever. It's not only lazy loading them, but it's trying to load different sizes based on the client. Not sure if anything they do would be better than just using optimized jpegs and settling on one size.