Hi, thanks for the reply.
You’re right, I guess the reason for creating that additional image is because this isn’t the real code, it was written just to highlight the issue.
As far as the issue, you’re saying that it is caused by Safari not utilising the pre-loaded image and instead firing another network request to get that image again when is added to the DOM? After checking the network tab I think you’re right :) (Seems to cache regular images and fail only when image is proxied through the deelay service?)
Could you please confirm if my understanding of your answer is correct :)
Thanks !