# Cache control immutable features

**URL:** <https://forum.inductiveautomation.com/t/cache-control-immutable-features/61410>\
**Category:** Ignition\
**Created:** [June 30, 2022, 6:36pm UTC](https://forum.inductiveautomation.com/t/cache-control-immutable-features/61410 "2022-06-30T18:36:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\
**Post date:** [June 30, 2022, 6:36pm UTC](https://forum.inductiveautomation.com/t/cache-control-immutable-features/61410/1 "2022-06-30T18:36:05Z")

</div>

I was reading about some ways that website speed up the loading.

One ways is by noting pages or parts of pages that do not change.

Is there a cache control feature in Ignition that I am not aware of that could speed up my page loads?

Or is that something only being done on the backend that I don’t really control in the designer?

---

<div class="post-metadata">

**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\
**Post date:** [June 30, 2022, 7:42pm UTC](https://forum.inductiveautomation.com/t/cache-control-immutable-features/61410/2 "2022-06-30T19:42:40Z")

</div>

> [@Perspective components internal loading](https://forum.inductiveautomation.com/t/perspective-components-internal-loading/61341/4):
>
> There’s no way to know when the component is done, because in the strictest sense it’s not Ignition (Perspective) that’s taking the 10-20 seconds. The property assignment is instantaneous, but after the assignment there are several factors which all add to the amount of time: The Gateway has to send all of the data to the browser through the websocket. Like a pipe, there’s only so much data which can be sent at one time - the data sort of backs up and comes through in chunks. The browser recei…

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 30, 2022, 8:22pm UTC](https://forum.inductiveautomation.com/t/cache-control-immutable-features/61410/3 "2022-06-30T20:22:19Z")

</div>

Cache control headers at the browser level don’t apply to Perspective, because it’s a single-page-application. From the web browser’s perspective (🕶) there’s only one primary request being made, when you first launch the session. _All_ other navigation inside the project is using the same set of assets & communication over the websocket.