The short answer is to just implement a cache of some sort and not be hitting the actual image directly every time you want to display it outside of the first time, per client or whichever level of service you’re using.
While I can only speak from mobile app client level experience, I assume there are similar web app/server concepts:
For example, in iOS you might use something like Kingfisher or SDWebImage which allows you to load the image in the UI and it handles all the caching under the hood.
In Android you might use something like Glide for the same thing as mentioned above.
1 Like