Front.space vs. ImageKit.io

E-Commerce is a perfect example where a service like ImageKit.io, is well suited. It takes a lot of the guesswork related to browser image format support, correct image dimensions for every kind of device, away from the developer. Thus reducing the need for maintaining code ourselves to check for and deliver an image for every user and his specific browser. This reduces code maintenance time in the long run and less custom code will ensure stability after integration for our online store running on OpenCart 3.

Incentivized

• Automatically convert images for fast delivery based on browser support and network quality.
• Well-documented integration documentation that is easy to follow when getting started with your implementation.
• Easy to navigate user dashboard for setup and management of server origins and account settings. The usage analytics page is also handy to track and fix any 404 errors there might be for an image/s.

Incentivized

• The Usage Analytics page could be laid out a little better and include filtering options, options may include path, country, IP Address, etc.
• The ability to add an additional user to the starter plan would be great to illustrate the possibility to new customers.
• The API Reference guide could include some more section-specific code examples for each of the supported technology stacks.

Incentivized

The main consideration for our choice was to be able to optimize and deliver the images from the server they are stored on without needing to move or change the current product upload workflow for our Marketing team. This is where ImageKit.io provided the best solution at the time we evaluated the options available in the market.

Incentivized

• Our code has become easier to maintain, we no longer need to let the backend generate thumbnails
• Our site speed up significantly, which boosted our SEO ranking
• We had a similar solution built in-house on AWS lambda, but we no longer have the headache to maintain this solution ourselves.

Incentivized