# 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:** 4\ **Page:** 1
**Author:** ![bennettan](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@bennettan](https://forum.inductiveautomation.com/u/bennettan)\ **Post date:** [March 10, 2020, 2:58am UTC](https://forum.inductiveautomation.com/t/lag-issue-page-loading-and-indication-feedback-slow/32957/1 "2020-03-10T02:58:06Z")
The page loading when switching page took about 11 seconds to complete the load. The response of the pushbutton and the indication which take 5 to 8 seconds. It is very obvious for the larger site which has more items or functions in one page as the print screen attached. All the Tanks and MOVs have popup window function. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/0274300371b2da4427b09dc2e41995cfee7a373e.png) Is there a way that can improve this issue? Ignition version used is 7.9.8, run on Dell PowerEdge R630 Server with Xeon E5-2620, 8G Ram and RHEL 7.3. 4 Clients PC. ---
**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, 5:53am UTC](https://forum.inductiveautomation.com/t/lag-issue-page-loading-and-indication-feedback-slow/32957/2 "2020-03-10T05:53:17Z")
Are you using UDTType parameters in your template(s)? These would most likely be the culprits here. I never use UDTType parameters, and will always pass in the tag path for my templates, for many reasons not just performance. ---
**Author:** ![bennettan](https://avatars.discourse-cdn.com/v4/letter/b/b9e5f3/32.png) [@bennettan](https://forum.inductiveautomation.com/u/bennettan)\ **Post date:** [March 10, 2020, 9:01am UTC](https://forum.inductiveautomation.com/t/lag-issue-page-loading-and-indication-feedback-slow/32957/3 "2020-03-10T09:01:06Z")
Yes, I did use UDT Type parameter. Which make life easier when adding new section. Our site, different section will have different connection. So, your idea is don’t use UDT Type Parameter? How about UDT type tag? Because 80% of the tags is UDT type. ---
**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…