Imagify not convert to webp

Hi @maxpalnet

If the WebP is chosen and you compressed images afterward, WebP should be generated. You can check this by appending the “.webp” to image URL so it would look like:
https://yoursite.com/wp-content/uploads/2024/05/image.jpg.webp

If it exists, there are a few reasons why Next-Gen formats will not be displayed using picture tags:

– background images added via CSS
– there is no Next-Gen format generated
– page element HTML is loaded after Imagify looks for the source code to apply Next-Gen markup
– images are external

And there are a few main reasons for this to fail using rewrite rules:

– you are on NGINX and didn’t apply custom rules to nginx.conf file manually
– image is missing a Next-Gen version (check by opening the image in browser and append “.webp” or “.avif to its’ URL
– mod_rewrite is not active on the server (Apache)
– image is external so it can’t be rewritten

Can you tell me if you can find a relation to some of these points? If not, can you send me your website URL so we could check it further?

Best Regards
Marko

it is converting but i have a problem its very slow, and its not optimizing

i read this article https://imagify.io/documentation/optimization-is-stuck/

i install the plugin Imagify Tools Infos

and i see this :

Max execution time 0

i talked to my host support and they change it to 300 , but it still not working, error

Hey @maxpalnet

Sorry to hear that! The 0 value is infinite actually so that should not be a problem. Do you use Imagick module (you can see this in Info page of Imagify Tools)? And what is the WP Memory Limit?

If it’s Imagick used and Memory is lower than 256M, you can try the following:

? Install our Don’t Use Image Magick helper plugin to have your server use an image manipulation module called GD, as when Imagick is used, it can sometimes make optimization very slow or not work well (works simply by activating).

? Add the following to your wp-config.php file (before the “That’s all! Stop editing…” message) to increase the amount of memory (this can be a larger number if your host/server will allow):

define( ‘WP_MEMORY_LIMIT’, ‘256M’ );

If that does not help either, can you ask your host if they have any firewall or other rules that might block this action?

Best Regards
Marko

hello

i talked to my host support about the value 0 and as i told you they changed it to 300

and they added to me this code define( ‘WP_MEMORY_LIMIT’, ‘256M’ );

and this is since 5 days ago

but i still see red color ( Max execution time 0 ) now its optimizing photos and but sometimes it take a long time,

now i visited Imagify Tool , to see if i use Imagick module, . and i see this, without red color:

Image Editor Component:

Selected Image Editor Imagick Should be Imagick or GD most of the time.
Imagick OK
GD OK

Shall I do something? Like using the add-on you sent me? Or is everything fine?

• This reply was modified 10 months, 1 week ago by maxpalnet.

I want to point that when I upload an image within the article, the browser freezes and then the page exits with a white screen: out of memory
On mobile, the page is refresh automatically and all i wrote is deleted
It also always shows me when i upload the photo , yoast seto: not available.

and this causes a big problem.

I note that I cannot disable ( the optimization option while uploading the image, ) because the site is news, and articles are published constantly. Is there anything I can do?
is this because of:
the value is shown to me is 0, i repead that i still see it in red color although the host changed it to 300
Or in this option:
Resize larger images Note that I set it to 2048 as written (You can save up to 80% after resizing. The new width should not be less than your largest thumbnail width, which is actually 2048px.)
Or in the option: Files optimization
What do I select from the list?

Hi @maxpalnet

Thanks for your patience!

the value is shown to me is 0, i repead that i still see it in red color although the host changed it to 300

You should make sure it’s not defined twice so the 0 value is overwriting the 300. Anyway, this is not a problem as 0 means infinite (no limit in timeout), and it will not cause the problem.

You can try to disable Resizing option, and also the main focus should go to check why 256M of memory is being used so easily. Imagify alone should not cause it so I believe it is combination of multiple tools.

Imagick is used as default module and it can be slow sometimes, so it would be good to follow the guide from my previous message:

??Install our?Don’t Use Image Magick?helper plugin to have your server use an image manipulation module called GD, as when Imagick is used, it can sometimes make optimization very slow or not work well?(works simply by activating).

Let me know how it goes.

Best Regards
Marko