Reasons for slow/laggy editor

mossi · 2025-05-05T21:40:44.493+00:00

Could someone shed some light? What exactly contributes to slowing down the editor? Is it the number of elements, depth of nesting, volume or complexity of formulas, actions, workflows, API calls, hardware (ram, cpu, etc)...? I’m hitting some excruciating lag in certain pages and components. In my case, it seems the number of elements causing the lag. Strangely, everything renders and performs fine in the browser — it's just the editor that's crawling.

mossi
8 months ago
Could someone shed some light? What exactly contributes to slowing down the editor? Is it the number of elements, depth of nesting, volume or complexity of formulas, actions, workflows, API calls, hardware (ram, cpu, etc)...? I’m hitting some excruciating lag in certain pages and components. In my case, it seems the number of elements causing the lag. Strangely, everything renders and performs fine in the browser — it's just the editor that's crawling.
Max
8 months ago
It's all the things you've mentioned 😄
Having a large element tree is propably the main reason why people experience lag. Structuring you app into smaller components helps a lot
Andreas Møller
7 months ago
Number of elements can slow down the editor for very large pages or components though most of the time performance issues are in the application being built.

Check if you are loading large amounts of data from an api etc.
mossi
7 months ago
There is very minimal api interaction in this particular page (just an auth and one POST). But there are a few forms with some forms begin somewhat long with 15, 20 fields. Some of the forms may be repeated by user or onload conditions. Attached is the top-level veiw of my project structor.
@Max Does moving some of the forms in a child componenet, like how I did for the "form-crim" help in my case? If that's the way to go, how would I pass an index of a repeated fotm input back to parent component? (I need the index of each field)
@mossi
There is very minimal api interaction in this particular page (just an auth and one POST). But there are a few forms with some forms begin somewhat long with 15, 20 fields. Some of the forms may be repeated by user or onload conditions. Attached is the top-level veiw of my project structor.
@Max Does moving some of the forms in a child componenet, like how I did for the "form-crim" help in my case? If that's the way to go, how would I pass an index of a repeated fotm input back to parent component? (I need the index of each field)
Max
7 months ago
Yes, this will very likely help. Makes sense to have a component for each form and include its logic in there, too. You pass info via attributes / events or contexts. You can find those in the docs:

https://docs.nordcraft.com/components/interface-and-lifecycle#component-interface

Reasons for slow/laggy editor

mossi

Max

Andreas Møller

mossi

Max