# How do you increase performance for clients?

**URL:** <https://forum.inductiveautomation.com/t/how-do-you-increase-performance-for-clients/62703>\
**Category:** Ignition\
**Created:** [August 4, 2022, 8:44pm UTC](https://forum.inductiveautomation.com/t/how-do-you-increase-performance-for-clients/62703 "2022-08-04T20:44:33Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [August 4, 2022, 9:45pm UTC](https://forum.inductiveautomation.com/t/how-do-you-increase-performance-for-clients/62703/3 "2022-08-04T21:45:22Z")

</div>

@pturmel's points address improving performance. If Perspective, this method makes things look a lot better during navigation by hiding the invalid states while waiting for data to arrive:

> [@\[Feature-1147\]Perspective - Delay Binding until custom property bindings have been evaluated](https://forum.inductiveautomation.com/t/feature-1147-perspective-delay-binding-until-custom-property-bindings-have-been-evaluated/43947/7):
>
> @chi we delay the initial display for simplicity. Most cases for us the evaluation takes \<1s but we have got some animations that hide for 2s then fade in for 1s on the particularly complex displays. This technique works particularly well for dynamically embedded views (I’m finding embedded views are still a little bit laggy, but I know that various solutions are being discussed by Ignition dev/support). If you have a fade in on the embedded view component and the child views, it hides the init…

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-do-you-increase-performance-for-clients/62703)._