Sorry I added images but they did not upload.
When you upload a JPEG image, then the original JPEG should be located in the Media Library. The plugin will then generate WebP/AVIF versions of that underlying JPEG. When you add the image to a post on the frontend you should see that a WebP/AVIF file is actually used in the IMG tag. That’s what I see.
The generator meta tag is essential for us to identify sites using the plugin to then measure the performance impact. This enables us to see whether the plugin is contributing to better performance on the web when we query sites in HTTP Archive.
Hey Weston – Thanks for the speedy reply. Yep you’re correct it is correctly generating WebP/AVIF I just wondered why the filesize only reduces slightly compared to when I use imagemin npm package.
Even still though cool feature!
Regarding the meta tags – is there not a better way to track usage via active installs or similar and not be intrusive to the <head> element?
Hey Weston – Thanks for the speedy reply. Yep you’re correct it is correctly generating WebP/AVIF I just wondered why the filesize only reduces slightly compared to when I use imagemin npm package.
It depends on the images being compressed and it might be due to outdated WebP/AVIF image PHP libraries being installed.
Regarding the meta tags – is there not a better way to track usage via active installs or similar and not be intrusive to the element?
The thing is that we need to identify the specific sites that are using the plugin when analyzing sites in HTTP Archive. It’s not really helpful to know the install count. We want to be able to compare sites that have the plugin active versus those who don’t and how the relative performance of images on the two sets of sites. In order to do this there needs to be an indicator the plugin installed, such as a meta tag. Elementor, WooCommerce, and Site Kit also output meta generator tags, as do many other plugins.
