dotnet-webassembly VS squoosh

there's a nuget WebAssembly package, so you can probably run assemblyscript on .net already.

It's been done

Things related to whatever you have used till now: 1- Don't use spaces in images name (Kind of code convention or sometimes automated tools tend to break) 2- Here is an opportunity to learn more about image types i.e, webp, aviff and more. (You can try squoosh.app) 3- Where to places JS scripts (it comes under perfomance section). Devs prefer to fetch scripts at the end of the body (Depends on use case but majorly). Understand about defer and sync. 4- Bootstrap is not a preferred tool now. Devs are moving to solution like tailwind. Tho, prefer to learn vanilla css and scss first. 5- Learn media queries, flexbox (for responsiveness) 6- If comfortable with flexbox then move to CSS grid 7- May be you can use https://flexboxfroggy.com/ and it has for grid too.

https://squoosh.app is a good cross platform option.

Squoosh - Visual image compression

Have you tried Squoosh to find the best compression settings visually? I'd be very curious to see how they compare.

I'd say that a proper OR recommended approach towards optimizing images for the web is to manually compress them with compression tools like TinyJPG or Squoosh before uploading them to your favorite image CDN. Why? you'd ask me.

This is the easiest measure you can do to improve your performance. You probably want your users to view the images in the best quality, but at what cost and is it necessary? If you serve an oversized image only to be viewed in a limited-sized box, you transfer unnecessary data over the network that take extra time before it can be displayed. I recommend you use a tool to resize and compress your image, e.g. Squoosh.