The compression level as well as optimized image quality is under your full control. With Image Optimizer extension, the users can set the quality percent they would retain after the compression process with slight visible loss in image quality. However, the biggest con is the loss of quality. The biggest advantage of lossy impression is the significant reduction in file size. Meanwhile, Custom (Lossy) compression means that there is the loss of data of the original image file. The trade-off is that there is little decrease in file size. Lossless will remove unnecessary meta data from image files. Lossless is a filter that compresses the data, which allows you to retain image quality while reducing the file size. Two types will bring out the difference in image quality and file size. IO-enabled requests that ultimately load an image from origin will transit the shield fetch node twice. ![]() IO interacts with the fetch node in the shield POP (see clustering and shielding ). There are two compression options: Lossless and Custom (Lossy). The Fastly Image Optimizer (IO) manipulates and transforms images as they pass through the Fastly network, and caches optimized versions of them. ![]() We recommend rst to run the test image optimization process with the 'multi-process' ON and monitor your server performance. But it generates extra load to the server as well. Multi-Process Optimization signicantly boosts the image optimization speed. By doing so, we set the amount of time for web browsers to keep images, CSS, and JS files stored, which lowers data usage. The most interesting feature of Image Optimizer is allowing store admins to set compression level. Enable Multi-Process Generation - select Yes to speed up images optimization. Image optimization quality - Lossless or Lossy
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |