Large image assets in /public directory (5MB–12MB) slow down cloning

[unclebay143]

I noticed that several image and screenshot assets in the /public folder are quite large (some around 5MB–12MB).

This makes cloning, forking, and contributing to the project resource-intensive, especially for those with limited bandwidth or system resources.

Would it be possible to optimize these assets or consider moving them to an external host/CDN or reducing their sizes using https://tinypng.com?

[Arshhasan]

Yes good I idea , I propose imgbb.com

[Arshhasan]

Or amazon S3 if we r looking for more reliable provider