imagekit-vuejs VS e-commerce-scully-example

Having the server decide the image format based on the accept header is simpler. Services like https://imagekit.io/ (no affiliation) can do that for you.

Hosting wise, I would reccomend pythonanywhere.com, combined with either https://imagekit.io or https://cloudinary.com

Use any third-party service to store images like Cloudinary , imagekit etc... And store image URLs in your database. If you have fewer images you keep image URLs directly in your APIs

We'll be using Multer to handle file uploads on our server and imagekit will do all our media heavy lifting. I chose these tools because I just found them easier to use and the latter has a very elaborate documentation (and a free tier too 😋).

Angular now provides popular Image Loader configurations out of the box. In our e-commerce application example, we set up ImageKit with the provideImageKitLoader function, whose path argument is the default URL endpoint for an account.

I use imagekit.io since it's cheaper than the alternatives like Cloudinary and Imgix, lots of options in that space though.

imagekit.io ♥

I'm using imagekit.io to resize my images and the custom loader they provided.

The above links are created using the ImageKit.io CDN. They have a very good free plan to try out and get started with: 20 GB bandwidth & 20 GB media storage. They also integrate with many web platforms. See the screenshot below:

Well, using imagekit and a bit of JS, you can accomplish just that. Our goal will be to use imagekit's on-the-fly resizing capabilities to resize all the images used on our website before they are served to the final user.

In this blog post, we will take a look at the exciting new NgOptimizedImage directive and explain how we used it to make this example e-commerce application perform up to 50% better on Lighthouse scores!

As a bonus, I’ve setup an E-Commerce example app (deployed with ng build && scully) where I used Scully to pre-render the content so you can see how the output looks using your browser’s DevTools. And you can compare it with a second E-Commerce no-Scully example app (deployed with ng build only), where the Scully pre-render step is not used. By the way, here's the GitHub repo.