Editor Slow - how can I figure out the cause?

  • lennartblmn

    6 days ago

    I'm aware that the editor gets slowed down by things that will also slow down the app itself.
    Almost sure it's some custom action, that I'm calling repeatetly and is not getting cleaned up or something - but I just don't know which. It also happens on a page, where I don't use any custom actions, even after a full reload.

    This is not meant as a "slow editor" complaint, but rather as a "how can i quickly identify the cause" question

    Thanks!
  • Erik Beuschau

    5 days ago

    Good question @ 👍
    Here are a few ways you can start:
    - Check if there are any reported issues on the component/page in the [issues panel](https://docs.nordcraft.com/the-editor/issues-panel)
    - If your component/page is slow. Create a new branch, and see if performance improves after deleting different things from it, e.g. onLoad/onAttributeChange workflows, APIs, large wrapping elements
    - Check if you're using overly complex test values for attributes (e.g. 1MB+ JSON payloads)
    - Check your developer console to see if there are any errors reported
    - Inspect your project using this (experimental) tool https://editor.nordcraft.com/page-size/<your-project-short-id>/<your-branch> to see if there are some components/attributes/variables etc. that stand out in terms of size. It's advised to keep the project's total size below 20MB if possible

    If none of those things help you identify the issue, the issue could be on our end and we're happy to investigate 🙌
    👍1
  • @Erik Beuschau
    Good question @ 👍
    Here are a few ways you can start:
    - Check if there are any reported issues on the component/page in the [issues panel](
    https://docs.nordcraft.com/the-editor/issues-panel)
    - If your component/page is slow. Create a new branch, and see if performance improves after deleting different things from it, e.g. onLoad/onAttributeChange workflows, APIs, large wrapping elements
    - Check if you're using overly complex test values for attributes (e.g. 1MB+ JSON payloads)
    - Check your developer console to see if there are any errors reported
    - Inspect your project using this (experimental) tool https://editor.nordcraft.com/page-size/<your-project-short-id>/<your-branch> to see if there are some components/attributes/variables etc. that stand out in terms of size. It's advised to keep the project's total size below 20MB if possible

    If none of those things help you identify the issue, the issue could be on our end and we're happy to investigate 🙌
    /attachments/1474077590930325628/1474339147329044490/Screenshot_2026-02-20_at_16.35.28.png

    Armand

    5 days ago

    That experimental tool looks cool!

    Sorry, for going a bit off-topic, but perhaps this is a good use case for seeing the size of the (test) JSON payload in attributes/vars directly in them (see image). It could also indicate when it's a bit much for editor performance.
    Screenshot_2026-02-20_at_16.35.28.png
    💯1
  • Erik Beuschau

    5 days ago

    Good suggestion. I also consider adding an (info level) issue rule to inform about this 👍
  • Armand

    5 days ago

    Should I add this in the suggestions channel?
  • Erik Beuschau

    5 days ago

    That's not necessary. I'll add the suggestion internally right now 👍 Should be simple enough 🤞
    👍2
  • @Erik Beuschau
    Good question @ 👍
    Here are a few ways you can start:
    - Check if there are any reported issues on the component/page in the [issues panel](
    https://docs.nordcraft.com/the-editor/issues-panel)
    - If your component/page is slow. Create a new branch, and see if performance improves after deleting different things from it, e.g. onLoad/onAttributeChange workflows, APIs, large wrapping elements
    - Check if you're using overly complex test values for attributes (e.g. 1MB+ JSON payloads)
    - Check your developer console to see if there are any errors reported
    - Inspect your project using this (experimental) tool https://editor.nordcraft.com/page-size/<your-project-short-id>/<your-branch> to see if there are some components/attributes/variables etc. that stand out in terms of size. It's advised to keep the project's total size below 20MB if possible

    If none of those things help you identify the issue, the issue could be on our end and we're happy to investigate 🙌

    lennartblmn

    5 days ago

    thanks! i will try and apply that
    🙌1

Stop scrolling. Start building.

toddle is a visual web app builder that rivals custom code — but accessible to your entire team!

Try toddle — it's free!

© Copyright 2024 toddle. All rights reserved.