# A Recent Experiment for App Speed

**URL:** <https://community.weweb.io/t/a-recent-experiment-for-app-speed/8016>\
**Category:** Tips and Hacks\
**Created:** [April 9, 2024, 1:28pm UTC](https://community.weweb.io/t/a-recent-experiment-for-app-speed/8016 "2024-04-09T13:28:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chadsmithclt](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@chadsmithclt](https://community.weweb.io/u/chadsmithclt)\
**Post date:** [April 9, 2024, 1:28pm UTC](https://community.weweb.io/t/a-recent-experiment-for-app-speed/8016/1 "2024-04-09T13:28:34Z")

</div>

Hi Community!!

Curious if anyone has gone down this path before. I was recently inspired by Linear.app’s approach to speed where they used IndexedDB api to get \<50ms response times between pages.

There is an inherit lag when switching pages in WeWeb and loading new data, so my recent approach has been to send my users to a “loading” screen after login where I fetch 10+ collections on page load and then navigate them to the home screen when complete. The experience is quite nice and the app is much faster, but the second part of this journey is posting updates to the DB.

Currently I am storing all user changes, as much as possible, in an Array variable instead of making a direct DB call, and then POST to a “Staging” table in Xano where I can handle DB changes every 60 seconds via a Xano Task.

@Broberto @caffeinatedwes @jptrinh any thoughts on this approach? Any other best practices you can think of?

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [April 9, 2024, 1:35pm UTC](https://community.weweb.io/t/a-recent-experiment-for-app-speed/8016/2 "2024-04-09T13:35:30Z")

</div>

> [@chadsmithclt](#):
>
> There is an inherit lag when switching pages in WeWeb and loading new data, so my recent approach has been to send my users to a “loading” screen after login where I fetch 10+ collections on page load and then navigate them to the home screen when complete.

Seeing this, the only thing I can suggest is delegate to a the backend more. It will probably gain you some speed 🙂