Encountered a strange thing. I have a page where the client can leave their offer for open ask. I organized this functionality through dynamic cards, which reflect all the necessary information about the open ask and contain a form for sending an offer.
From the point of view of logic, everything works perfectly. However, the problem is strong page brakes, the reason for which is not known.
I looked at everything that could cause a loss of speed, but found nothing. There is one relatively large query on the page, but it is optimized and loads quickly. The possible reason could be the lack of unique identifiers for dynamic elements, but I added a dynamic id to all such elements.
The drawdown in speed looks as if some incredible calculations are made at the DOM level when entering information in the form begins. And there is a very clear pattern: the more open asks are reflected on the page, the more active the speed loss begins to appear. Below I will give an example with only 13 open asks, if you open the ask and start entering any text in the form inputs, you will feel that the page starts to slow down. I’m afraid to imagine what might start in combat mode after the release, when there may be several hundred open asks…
Here is an example: http://crm.svk.center/counteragent.html?uniqcode=8eb8e273-444a-4790-92d2-4d3cb3342f16
If anyone has any ideas, I’d appreciate it.
@George, @patrick, @Teodor perhaps you have a simple answer to the problem? I may have overlooked something when designing the page using Wappler.
Last updated: