WebP is a modern and more economical image format that Google recommends to use instead of obsolete PNG and JPEG.
The only difficulty with using WebP is that not all browsers support it yet. Therefore, the solution "on the forehead" (convert all pictures to webp) - does not fit.
The use of WebP fits in perfectly with our CDN format.
How it works:
When requesting each image by a site visitor CDN OptiPic determines whether the visitor’s browser supports WebP format .
If supported, the image is rendered as WebP.
If not supported, the image is rendered in the old format (but at the same time optimized and compressed).
In this case, the WebP version of the image is generated completely in the background on the CDN side - the visitor / browser does not wait for each image to be converted to WebP.
No WebP support.
All images remain in the original format (png / jpeg) after optimization.
Google PageSpeed Insights determines that images are correctly compressed and optimized for the modern WebP format.
Images are correctly indexed by search engines, linked to your site, and are searched for images by your domain.
URLs of images are changed - now they will lead to OptiPic CDN. If you need to leave the URL unchanged, you can use the universal connection via Nginx (proxying) or connect the OptiPic CDN to your subdomain (for example , img.site.com).
Google PageSpeed Insights determines that images are correctly compressed, but strongly recommends using the more advanced WebP image format.
Images are correctly indexed by search engines, linked to your site, and are searched for images by your domain.
CDN gives the picture in an additional lightweight version for mobile, if requested from a mobile device.
If the picture is requested from a regular computer (PC), then the CDN gives the picture without further relief.
There is no support for mobile devices - pictures are given the same way for both mobile and PC.
Optimization takes place entirely on the side of our CDN.
The index database on your site is not created, not stored, not updated.
Only links to optimized versions of images in our CDN are indicated on your site.
URLs of images are changed - now they will lead to OptiPic CDN. If you need to leave the URL unchanged, you can use the universal connection via Nginx (proxying) or connect the OptiPic CDN to your subdomain (for example , img.site.com).
Image traffic goes through our CDN, additionally removing even this load from your hosting.
The process of image optimization takes place on the side of our API.
The "index" database (i.e. a list of all the pictures on your site) is stored and periodically updated / read from your database running Bitrix.
This adds to the load on the hosting hard drive, as well as the site database (MySQL) compared to CDN.
Image traffic goes through your hosting, creating a load on it.
CDN takes on this task entirely.
Images from CDN are rendered as efficiently as possible. Various caching mechanisms are also used to speed up data transfer to the browser.
Images will not be converted, optimized and compressed on the fly every time with each request. CDN will conduct all these procedures once for the requested image in the background so as not to impede the delivery of images to the visitor of your site.
In the classic version of integration, your hosting / server takes on this task. Therefore, the effectiveness of the image transfer depends solely on the optimal settings of your server / hosting.
Payment is taken for image views.
This option is the most transparent - you only pay for viewing the images that are displayed to visitors to your site.
If the pictures are in the folder with the site, but are not displayed anywhere on the site, you do not bear the cost of optimizing them.
You pay in proportion to traffic to your site.
At first, when your site’s traffic is low, then the number of views of images on it will be minimal.
And when you upgrade your site, and its traffic will already be good - you can afford to pay for a larger volume of image views, because the site will bring more revenue than it previously brought with low traffic.
Payment is taken for the effective compression of each image. Compression is considered effective if the weight (in bytes) of the compressed image is less than the weight of the original image before compression.
Moreover, the system cannot automatically determine which images in the folder of your site are actively used (displayed) on the site, and which are “dead weight” and displayed on the site extremely rarely or never at all. Therefore, all images on the site that the system found are compressed. And you can previously exclude unnecessary folders / files yourself by registering them manually in the system settings (or vice versa - register only those folders that need to be processed).