Once the images are cached, it should load quicker (2nd time onwards). If users are loading your app for the first time, they will have to load all the images and I imagine that increases your loading time. The time to process one image through Cloudinary (end result 400kb) is still faster in my observation than loading the original image from the original Googleapis link which has a file size of 2MB. It reduces the loading time by a few seconds. I don’t know if resizing with Cloudinary does help with loading time, but wouldn’t Cloudinary would still have to process your image first before pushing the final image to the user? I’m not sure if it’s because I’m on a free plan, but I have reached out to Cloudinary and I’m currently awaiting response from them. I have tried various ways to change the Glide cloud name to mine but it doesn’t seem to work.
Normally, that “glide” part should be your Cloudinary user name. This is just a hacky method, you are actually using Glide’s account to transform your image. The ultimate reason is speed - reducing the loading time for users because my app is image-heavy and it is currently taking a long time to load.
0 kommentar(er)
