Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

232
Views
Ninja Forms front-end.js long task in Chrome Performance impacting Core Web Vitals

In Core Web Vitals, we have high Total Blocking Time and it seems the main culprit is this script in Ninja Forms. If it is commented out, Ninja Forms does not load - obviously not a solution. But I would love to figure out a way to stop it from impacting the load performance.

This seems to be the specific code in front-end.js causing it:

//Simulate async callback;
if (forceSync) {
  main(undef, deps, callback, relName);
} else {
  //Using a non-zero value because of concern for what old browsers
  //do, and latest browsers "upgrade" to 4 if lower value is used:
  //http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#dom-windowtimers-settimeout:
  //If want a value immediately, use require('id') instead -- something
  //that works in almond on the global level, but not guaranteed and
  //unlikely to work in other AMD implementations.
  setTimeout(function () {
      main(undef, deps, callback, relName);
  }, 4);
}

return req;

Code

Performance:

Performance

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!