Performance issues with delayed calculation updates and repeated image requests

  • mlchrt

    (@mlchrt)


    4 days, 11 hours ago

    Hi Forminator Support Team,

    I’m experiencing two issues with Forminator in a very large and complex form. The form contains many conditional visibility rules, several calculation fields, and calculation fields that depend on other fields or other calculated values.

    Because the form contains sensitive business data and internal logic, I unfortunately cannot share a public export of the full form here. However, I would like to understand how I can debug these issues properly and whether there are any known limitations, similar reports, or recommended best practices for large Forminator forms.

    Environment / Context

    The issues occur in a very extensive Forminator form with:

    • Many conditional visibility rules
    • Several calculation fields
    • Nested or dependent calculation logic
    • HTML fields
    • A large amount of form display logic

    The issues mainly appear in this complex form structure.

    Issue 1: Calculation fields update with a very long delay

    The form does not feel smooth during use. The main problem is that calculation fields do not always update in sync with the user’s progress through the form.

    In some cases, calculated values are updated much later than expected. To investigate this, I added a small custom debug script that logs when calculation fields receive updated values.

    Example debug output:

    Some calculation fields are updated after around 6 seconds, while others are updated much later. The affected calculation fields are partly nested or depend on other fields/calculation fields, but I cannot identify why the delay is so extreme.#

    [Calc] val set on calculation-48 = 6,10 @ 6433.5ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-33 = 0,00 @ 6440.5ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-34 = 0,00 @ 6444.0ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-23 = 1280,43 @ 426573.9ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-9 = 1280,43 @ 426576.4ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-52 = 1370,06 @ 426577.7ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-51 = 1280,43 @ 426579.0ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-38 = 3123 @ 426580.1ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-50 = 3123.00 @ 426583.7ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-44 = 6,10 @ 437439.8ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-9 = 1286,53 @ 437441.4ms

    forminator-calc-debug-js-after:26 [Calc] val set on calculation-52 = 1376,59 @ 437442.3ms

    Questions about Issue 1

    1. Is there a known performance limit or practical recommendation for the number of conditional rules and calculation fields in one Forminator form?
    2. Can nested or dependent calculation fields cause delayed recalculations in large forms?
    3. Is there a recommended way to debug the internal calculation flow or calculation triggers?
    4. Are there any hooks, JavaScript events, or debug settings that can help identify which field, condition, or formula is causing the delay?

    Issue 2: Image inside an HTML field is requested repeatedly

    The second issue happens when I insert an image inside an HTML field using a regular <img> tag.

    When the image is rendered through the HTML field, the browser requests the same image repeatedly in a long loop. In one test, the same image was requested roughly 200 times before the requests stopped.

    This only happens when the image is inserted through the Forminator HTML field. I currently do not know what triggers the repeated loading behavior.

    GET https://example.com/recaptcha__de.js          text/javascript   trigger: https://example.com/webworker.js?hl=de&v=U5Vsm...   duration: 47 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 114 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 73 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 72 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: Other                                             duration: 43 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: Other                                             duration: 93 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: Other                                             duration: 68 ms
    GET https://example.com/forminator-icons-font.woff2 font            trigger: https://example.com/forminator-icons.min.css?ver=1   duration: 42 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 73 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 70 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 73 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 72 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 71 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 71 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 71 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 82 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 72 ms
    GET https://example.com/example.jpg               image/jpeg        trigger: https://example.com/jquery.min.js?ver=3.7.1:2        duration: 71 ms
    GET https://example.com/example.jpg               image/jpeg        trigger:

    Questions about Issue 2

    1. Is there any known issue with images inside Forminator HTML fields, especially in large forms with many conditional rules?
    2. Could conditional rendering or repeated field refreshes cause the HTML field content to be re-rendered repeatedly?
    3. Is there a recommended safer way to include images inside Forminator forms?
    4. How can I debug which Forminator event, condition, or field refresh is causing the image to be requested so many times?

    Main question

    Could you please advise what the best way is to debug these two issues further?

    I would also appreciate any information about known limitations, similar reported issues, or recommended performance practices for very large Forminator forms with many conditions and calculation fields.

    Thank you for your help.

Viewing 1 replies (of 1 total)
  • Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    3 days, 21 hours ago

    Hi @mlchrt,

    Is there a known performance limit or practical recommendation for the number of conditional rules and calculation fields in one Forminator form?

    Can nested or dependent calculation fields cause delayed recalculations in large forms?

    If there are many conditional fields and calculations, this can cause such behavior. However, such use cases are highly common depending on the field and its setup, so what we can comment on about the exact cause is limited.

    In case you think if its possible to share the form export privately then you can use share it to the following email  wpsupport@incsub.com  using this template to share the site URL:

    Subject: ATTN: WPMU DEV support - wp.org 
    Message:  
    Ticket URL
    URL to download the form export

    Is there a recommended way to debug the internal calculation flow or calculation triggers?

    You could check the browser console for any errors that might give a clue:
    https://developer.wordpress.org/advanced-administration/debug/debug-javascript/#open-the-developer-tools


    However, in general, I’m afraid there isn’t an easy workflow to rule it out, other than duplicating the forms and checking how it behaves by deleting specific fields to see if that improves the form’s load. That should help identify which fields to rule out for further investigation.

    If the form is quite large with a lot of conditions and calculations, then it would be better to consider splitting up the form into multiple forms and add a redirection on submission from 1st form to 2nd form with pre-populated values.

    Please check this for more info:

    https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#pre-populate-form-field-values

    When the image is rendered through the HTML field, the browser requests the same image repeatedly in a long loop. In one test, the same image was requested roughly 200 times before the requests stopped.

    Sounds like an issue specific to your site. I’m not able to replicate such an issue when tested in my system, are you able to replicate the same in a new form?

    Could you please setup a staging site and check if you could replicate the same issue if all the plugins are disabled except Forminator and with a default WP theme to see the issue with images is the same or not?

    Looking forward to your response.

    Regards,

    Nithin

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.

Tags