When you push URLs from an image provider, it is not easy to use something like Sharp to optimize your imagesĪ good explanation from Gatsby when optimizing your images which you can read it here
The problem is that I have been pushing really big images which are slowing down the site My biggest purpose of using an image provider is to decrease the bundling size of my site by not cluttering it with images also Forestry does an amazing job pushing the Cloudinary URLs inside of the blogpost markdown file without adding more configurations and plugins to my Gatsby site hence there was no problem at all from the setup side The setup isn't poorly optimized, the images on that setup are
MAC IMAGEOPTIM GENERATOR
My blog runs Gatsby as my static site generator along with Forestry as my git-based CMS but before you start telling me about plugins for Gatsby like gatsby-plugin-sharp, I am using Cloudinary as my image providerīut you might say that there are plugins for Cloudinary as well especially for Gatsby like gatsby-source-cloudinary and gatsby-transform-cloudinary which can solve the problem. Something was eating my resources and it was my images so I had to find a way to optimize them So today I have decided to optimize my blog. There are times where you can't use image optimization libraries so you have to do some compromises I have worked with designers before that they demand to have full resolution images on the site or the client pushes really big images. The purpose of this blog post is to shed some light on basic image optimization.
0 kommentar(er)
