Sorry I keep reporting bugs
But with the new focus on AI , there are many other things weweb used to be good at but now getting harder. this is one of them.
When my app loads , first thing people see is weird boxes for icons .. then the svgs load later changing boxes to the icons I set.
With the new change in icons , they seems to be lazy loaded.
Makes the app look unprofessional.
If it were images , we could have set load type to Eager
But icons dont have that options.
Please fix it.
Hi there,
I have the same issue with icons being lazy loaded. Could someone please look into this?
Many thanks in advance.
Hi there 
Icons on WeWeb apps aren’t lazy-loaded. If you check your icon element in the browser inspector, you should see it’s an inline svg:
Inline SVGs do not request external files. The SVG path data is already in the page’s HTML, so the browser has nothing to fetch.
That said, we have seen occasional cases where icons appear to “blink” or show up a moment late. This typically happens in one of two situations:
Even though the SVG is inline, the HTML itself can take noticeable time to download on extremely slow networks. Until the HTML arrives, the icon can’t render.
If your icon is dynamically bound (e.g. via a data object that starts empty and gets populated on page load), the browser will first render an empty SVG and then update it once the data arrives.
The solution for this: Ensure that the bound object includes a default path so the SVG isn’t empty on initial render.
Does that help?
If not, can you create a support ticket here with more information about your project so that our team can take a closer look?
