# Lag Issue, Page loading and indication feedback slow **URL:** \ **Category:** Ignition\ **Created:** [March 10, 2020, 2:58am UTC](https://forum.inductiveautomation.com/t/lag-issue-page-loading-and-indication-feedback-slow/32957 "2020-03-10T02:58:06Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [March 10, 2020, 9:15am UTC](https://forum.inductiveautomation.com/t/lag-issue-page-loading-and-indication-feedback-slow/32957/4 "2020-03-10T09:15:27Z")
UDT tags are great, but template UDT type parameters are not. > [@To UDT or not to UDT. That is the question](http://forum.inductiveautomation.com/t/to-udt-or-not-to-udt-that-is-the-question/32703/15): > > at a glance, it’s not possible to see by looking at a component’s properties which UDT instance has been bound to a UDT type property. E.g. in the screenshot below, I have no idea which Tower UDT is bound, I have to click on the binding to find out. It’s also far slower to populate template parameters than simply modifying a parameter string value. I tend to use 2 parameters: DeviceParentPath and DeviceName, then combine these together in an internal parameter DeviceTagPath, which also aids in… --- _[View the full topic](https://forum.inductiveautomation.com/t/lag-issue-page-loading-and-indication-feedback-slow/32957)._