Description
In Imagify settings, the tag method is marked as “preferred” for loading next-gen images and is selected by default.
This method replaces ![]()
tags with tags, which can cause compatibility issues with certain themes or layouts. In practice, this sometimes leads to layout breakage, missing images, or unexpected behavior.
Although there is already a warning stating that some themes may break, many users do not fully understand the impact of this choice. As a result, users often proceed with the default option and later face layout issues, especially during first-time setup.
From the support side, we regularly receive tickets related to layout or display issues caused by the tag method. This is particularly problematic for new users, who may panic when their site layout breaks and immediately request a refund.
Additionally, based on support experience, rewrite rules often provide better and more consistent coverage for next-gen delivery on sites that are not using a CDN or Cloudflare.
For example:
• tags may not cover background images• Sliders and certain WooCommerce product pages can have issues depending on the theme
Points to Consider
• The warning message could be made clearer and more explicit about possible layout impact
• Linking to relevant documentation could help users make a more informed choice
• The “preferred” label on the tag method may need reconsideration, unless there is a strong technical reason for it
Most of the tickets are under this tag: https://secure.helpscout.net/search/?query=tag%3Aimg_broken_layout
Some of them:
https://secure.helpscout.net/conversation/3182151830/611108
https://secure.helpscout.net/conversation/3144083997/601349
https://secure.helpscout.net/conversation/3165293908/607395
https://secure.helpscout.net/conversation/3151973027/603818
Description tag method is marked as “preferred” for loading next-gen images and is selected by default.
In Imagify settings, the
This method replaces![]()
tags with tags, which can cause compatibility issues with certain themes or layouts. In practice, this sometimes leads to layout breakage, missing images, or unexpected behavior.
Although there is already a warning stating that some themes may break, many users do not fully understand the impact of this choice. As a result, users often proceed with the default option and later face layout issues, especially during first-time setup.
From the support side, we regularly receive tickets related to layout or display issues caused by the tag method. This is particularly problematic for new users, who may panic when their site layout breaks and immediately request a refund.
Additionally, based on support experience, rewrite rules often provide better and more consistent coverage for next-gen delivery on sites that are not using a CDN or Cloudflare. tags may not cover background images• Sliders and certain WooCommerce product pages can have issues depending on the theme
For example:
•
Points to Consider tag method may need reconsideration, unless there is a strong technical reason for it
• The warning message could be made clearer and more explicit about possible layout impact
• Linking to relevant documentation could help users make a more informed choice
• The “preferred” label on the
Most of the tickets are under this tag: https://secure.helpscout.net/search/?query=tag%3Aimg_broken_layout
Some of them:
https://secure.helpscout.net/conversation/3182151830/611108
https://secure.helpscout.net/conversation/3144083997/601349
https://secure.helpscout.net/conversation/3165293908/607395
https://secure.helpscout.net/conversation/3151973027/603818