Images in webp format with imagify.io

  • Resolved arafail

    (@arafail)


    4 years ago

    Hello!
    We are great fans of you plugin but we would however like to solve the following problem:
    1: We are using WordPress + Amp-wp + CloudFlre + Wp-Rocket + Imagify.io.
    2: Imagify has been added in order to serve images in .webp format.
    3: Imagify replaces the wordpress img tag with a <picture></picture> tag.

    The second option replaces the tags with <picture> tags. This is the preferred solution but some themes may break, so make sure to verify that everything seems fine.

    4: At the same time, your plugin wraps the tag in an <amp-img></amp-img>
    5: The problem is that the .webp files, although they exist on the server are not shown on the website, as you can see here: https://www.digitalcitizen.ro/creaza-cod-qr/

    Here are 2 versions of the same image:
    https://www.digitalcitizen.ro/wp-content/uploads/cod_qr.png
    https://www.digitalcitizen.ro/wp-content/uploads/cod_qr.png.webp

    Do you think that the problem here, with not .webp not being displayed is because of imagify/wp-worcket or because of amp-wp plugin?

    All the relevant plugins for this problem are updated at the latest version as is our wordpress instance.

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • James Osborne

    (@jamesosborne)

    Thanks for reaching out, glad to hear you’re enjoying the plugin. We did investigate methods to automatically convert picture tags to amp-img previously although any approaches didn’t provide a suitable outcome, you’ll find out more below:
    https://github.com/ampproject/amp-wp/issues/1316

    In relation to different versions of the same image I believe this may be standard behavior with your plugin, with one used as a fallback for non webp supported devices.

    When I check your homepage, which contains multiple images I noticed all in post images are being served in webp format, while also having their standard png accessible directly.

    You’ll find a similar support topic on webp and the <picture> tags here, with some additional insights based on another users experience.

    So to summarize I don’t see any issue with your current setup, but let me know if you have any further queries on this.

    Plugin Author Weston Ruter

    (@westonruter)

    Since amp-img doesn’t support source alternatives (though it has been discussed) and picture is not currently supported (but it will be), there’s not really a good option for doing this in AMP client-side.

    The recommended approach and best practice for serving WebP to supporting clients is to use content negotiation server-side. This is what you get when you use Jetpack’s Image CDN (Photon): it will serve WebP to supporting browsers or else JPEG et al to others.

    Plugin Author Weston Ruter

    (@westonruter)

    Note that over 90% of browsers support WebP now, so you also may want to consider just serving it exclusively.

    @arafail As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist. Thank you!

    Thread Starter arafail

    (@arafail)

    I am sorry for not responding.
    It is indeed ok.
    We just encountered many other issues with the project.

    @arafail Thanks for the update. Just let us know if you need us. ??

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Images in webp format with imagify.io’ is closed to new replies.

Tags