adeelkhan

Could you please explain the scenario a bit more to gain a better understanding?

Meanwhile, when the lazy load feature is enabled, it functions as follows: The images are initially replaced by a dummy transparent image acting as a placeholder. As these images come into view on the screen, the lazy load mechanism triggers the loading of the original images.
Additionally, the code recognizes attributes such as data-sizes and data-srcset, which are essential for displaying the correct image size based on the resolution of the device.

Thank you for your prompt response. From your message, I gather that the issue occurs when CSS minification is enabled. Please correct me if I have misunderstood.

To further investigate this matter, could you please check the console errors in the Browser Network Tab to see if any errors are displayed there? This will help us pinpoint the root cause of the issue and proceed with appropriate troubleshooting steps.

Your assistance in this matter is greatly appreciated.

Apologies for any inconvenience you may be experiencing. Our support team has promptly escalated your case to the Breeze team. They are currently investigating the matter and will reach out to you with updates shortly.

Thank you for highlighting the point. We will certainly address in our upcoming release.

I’m curious about your experience with speed optimization using Breeze. Could you share your insights?

Thank you for generously sharing your insights! Your input is truly appreciated. I’m keen to delve deeper into your experience with CSS and JS minification utilizing the Breeze plugin. If you could impart any thoughts or offer tips, it would be immensely valuable. Eagerly anticipating your response!

Yes of course.

Did you contact for support team about the issue?
If not so please contact our support and?create a ticket, we will thoroughly investigate the point of conflict and ensure to share our findings with our users. Your cooperation is much appreciated.

The issue has been fixed in 2.1.5.
Please update the latest version.

The reported issue has been successfully addressed and fixed in the latest version of our plugin. You can now update to version 2.1.6 to ensure seamless functionality and enhanced performance.

Apologies for inconvenience caused. We’re actively working on it and will provide an updated solution as soon as possible

Thank you for sharing your feedback. Your input has been duly noted and added to our feedback list. Rest assured, we plan to incorporate it in our upcoming feature releases.

I sincerely apologize for any inconvenience you may have experienced. To better assist you, could you kindly clarify whether your case has been forwarded to the Breeze team for investigation?

In order to expedite the resolution process, I recommend creating a support ticket specifically for the Breeze team. This will enable them to thoroughly investigate the point of conflict. If the issue is related to Breeze, rest assured that we are committed to resolving it in our upcoming releases.

Thank you for taking the time to share your valuable feedback.

We greatly appreciate your insights. In light of your comments, we are particularly interested in understanding your experience with Breeze functions, especially regarding HTML, CSS, and JS minification, and how they contribute to speed optimization.

If you could provide more details about the impact of these features on your speed optimization goals or any specific instances where you found them beneficial, it would be immensely helpful for our ongoing efforts to enhance and refine the Breeze plugin.

Your experience is crucial in helping us tailor our functionalities to better meet the needs of our users, and we look forward to hearing more about your insights.

Thank you for bringing the issue to our attention. We are aware of the conflict and will address it in our upcoming release. We appreciate your cooperation.