• Resolved 50M

    (@50m)


    How does using this plugin work in the case of a Cloudflare account that has multiple (MANY) domains/websites? Can I set up multiple Cloudflare Images accounts, or would all the domains share one? If shared, what are the ramifications? These are client sites, so I need to be careful here ??

    Is the AI functionality included with Cloudflare Images? I was unable to find any mention of AI being a feature of Cloudflare Images. If not, where does the AI functionality come from?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Anton Vanyukov

    (@vanyukov)

    Hi @50m,

    You can use a single account for all domains (that’s what I do), the image paths will have the site domain in the path, so there will not be any conflicts.

    No, the AI image tagging comes from Microsoft and Google, image generation is DALL-E 4 from OpenAI . The external CDN is from Bunny CDN. All those are handled via one my SaaS platform.

    Best regards,
    Anton

    Thread Starter 50M

    (@50m)

    Thanks for the reply, Anton. Can you provide more details re: “All those are handled via one my SaaS platform.”?

    Plugin Author Anton Vanyukov

    (@vanyukov)

    @50m,

    Sure, you can have a look here: https://getfuzion.io

    Best regards,
    Anton

    Plugin Author Anton Vanyukov

    (@vanyukov)

    Hi @50m,

    I’ll mark this thread as resolved. If you have any other questions, feel free to re-open or create a new thread.

    Best regards,
    Anton

    Thread Starter 50M

    (@50m)

    Hello again, Anton!

    Regarding image transformations using Cloudflare, i.e. having Cloudflare serve webp files instead of existing file formats like png & jpg, is there an easy way to add that functionality to your plugin?

    Plugin Author Anton Vanyukov

    (@vanyukov)

    Hi @50m,

    Cloudflare Images do this automatically – the best possible format will be served, regardless of the uploaded format.

    Best regards,
    Anton

    Thread Starter 50M

    (@50m)

    @vanyukov That’s what I thought, but, although images are being served by Cloudflare, they’re not being resized or served in a different file format like they should be. I have checked and double checked all settings for the plugin and on Cloudflare as well. Can I email you to discuss more details?

    Plugin Author Anton Vanyukov

    (@vanyukov)

    @50m, can you please provide an example image?

    You can contact me via the contact form here: https://vcore.au/contact-us/

    Thread Starter 50M

    (@50m)

    @vanyukov I submitted a contact form with reference link. Thank you.

    Plugin Author Anton Vanyukov

    (@vanyukov)

    @50m, I had a look. It’s not the format that is the issue – it’s the image dimensions. Can you please try to enable the “Use img width size” option in Media – Offload Settings in the “Parse page for images” module. That should fix the issue.

    Thread Starter 50M

    (@50m)

    @vanyukov?

    I sent you the updated SpeedVitals link via your contact form.

    I tried what you said, enabled “Use img width size”. I also tried it with and without “Auto resize images on front-end”, and I bulk removed, then re-Bulk offloaded the images. Same result. Images are being served via Cloudflare, just not resized and no file format changes either, even though WebP would be smaller in most/all cases.

    If it makes any difference, this is a Breakdance website:
    https://breakdance.com/documentation/developers/
    https://breakdance.com/documentation/

    What else can I try?

    Plugin Author Anton Vanyukov

    (@vanyukov)

    Hi @50m,

    I can see that the sizes have been fixed. You no longer have 9999px images, and the sizes are taken from the width/height attributes. Breakdance builder has its own unique way of managing content, a lot of the images are resized via CSS, and, unfortunately, there’s no way for my plugin to know that, because CSS is processed on the browser side, not server side. If you want to fix those remaining audits, you’ll need to adjust the sizes in Breakdance.

    Regarding WebP/AVIF. You can view the image headers, and it will tell you why the image is not served in a modern format. There’s really two reasons – the image is too large to be converted or the resulting image is larger than the original. For example, the tyres-spring-dating-email.png image is served as PNG, because in the image header you can see warning: cf-images 299 "original is 12767B smaller". Which means that if converted to WebP, the image would actually be larger than the original. This often happens with images that have a transparency channel. A fix could be to convert your PNG images to JPEG, then they are guaranteed to be converted to WebP/AVIF.

    Best regards,
    Anton

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Some General Questions’ is closed to new replies.