That’s good news! Resources contain a lot of overhead, so wherever possible try to limit the number of resources the parser has to loop through.
Am I right that those @EVALS are being used to populate dropdown lists in the manager, rather than for displaying on the front end? If that’s the case then they shouldn’t have any impact on the front end speed.
Am I right that those @EVALS are being used to populate dropdown lists in the manager, rather than for displaying on the front end? If that’s the case then they shouldn’t have any impact on the front end speed.
Yes the costumer can populate a dropdown list from the manager and the result gets displayed on the front-end, it works great and it’s fast to!
