# Bandwidth : how does that work?

**URL:** <https://community.weweb.io/t/bandwidth-how-does-that-work/21121>\
**Category:** How do I?\
**Created:** [April 26, 2026, 4:15pm UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121 "2026-04-26T16:15:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![MrUnfreeze](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@MrUnfreeze](https://community.weweb.io/u/MrUnfreeze)\
**Post date:** [April 26, 2026, 4:15pm UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/1 "2026-04-26T16:15:53Z")

</div>

Hello,

I’ve just published my app. I’ve the 20$ plan that includes 10 gb of bandwidth.

I had about 1000 connections which consumed 2.1 gb.

So my question is : how does consumption work exactly? What can I do to optimize consumption?

Thanks

---

<div class="post-metadata">

**Author:** ![Himanshu](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/himanshu/32/16305_2.png) [@Himanshu](https://community.weweb.io/u/Himanshu)\
**Post date:** [April 27, 2026, 5:32am UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/2 "2026-04-27T05:32:51Z")

</div>

Is your app a media-heavy platform with a lot of images and videos?

---

<div class="post-metadata">

**Author:** ![MrUnfreeze](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@MrUnfreeze](https://community.weweb.io/u/MrUnfreeze)\
**Post date:** [April 27, 2026, 9:50am UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/3 "2026-04-27T09:50:35Z")

</div>

No, 0 images or videos. Where can I monitor each page consumption per session of user? Maybe it could be API calls which load data ?

---

<div class="post-metadata">

**Author:** ![Himanshu](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/himanshu/32/16305_2.png) [@Himanshu](https://community.weweb.io/u/Himanshu)\
**Post date:** [April 28, 2026, 7:06am UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/4 "2026-04-28T07:06:31Z")

</div>

You can see the overall bandwidth in the app settings, but the bandwidth per user session wouldn’t be visible. You’d need to create your own way to track it.

Yes, API calls do take up bandwidth. What’s your backend?

---

<div class="post-metadata">

**Author:** ![MrUnfreeze](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@MrUnfreeze](https://community.weweb.io/u/MrUnfreeze)\
**Post date:** [April 28, 2026, 1:48pm UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/5 "2026-04-28T13:48:02Z")

</div>

I use Xano.

How do I know per page the bandwidth consumption? I can’t find it in the app settings.

Thanks

---

<div class="post-metadata">

**Author:** ![MrUnfreeze](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@MrUnfreeze](https://community.weweb.io/u/MrUnfreeze)\
**Post date:** [May 4, 2026, 5:57am UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/6 "2026-05-04T05:57:44Z")

</div>

@Joyce would you by any chance know?

Thanks

---

<div class="post-metadata">

**Author:** ![Slavo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/slavo/32/13253_2.png) [@Slavo](https://community.weweb.io/u/Slavo)\
**Post date:** [May 4, 2026, 3:57pm UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/7 "2026-05-04T15:57:19Z")

</div>

Hi @MrUnfreeze! With no images or videos, your bandwidth is going to three places:

1. **The WeWeb app bundle itself** - the JS, CSS, and fonts that make up your app. On first visit, every user downloads this. Depending on how many components/plugins you use, this is typically 1–3 MB per fresh visit. If you had 1000 sessions and many were first-time visitors (or returning users with cleared caches), that alone could account for most of your 2.1 GB.

2. **Xano API responses** - every workflow call returns JSON, and JSON adds up fast if you’re returning whole records when you only need a few fields, or fetching long lists without pagination.

3. **Other assets** - custom fonts, icons, any files served from your domain.

A few things worth checking:

- **Audit your Xano endpoints.** Open the browser DevTools → Network tab → filter to “Fetch/XHR”, then click through your app like a normal user. You’ll see every API call and its exact size. Look for responses that are bigger than they need to be - usually it’s an endpoint returning 50 fields when the page only displays 5, or a list query returning all records instead of paginating.

- **Trim your Xano response shapes.** In the Xano function stack, use the Output tab to return only the fields the page actually needs.

- **Paginate long lists.** If a collection list shows 20 items at a time, your endpoint should return 20, not all 500.

- **Avoid polling and aggressive `on page load` refetches.** If two collections refetch on every page mount, navigating around the app multiplies bandwidth quickly.

- **Reuse collections across pages.** A collection fetched once at app level doesn’t need to be re-fetched on every page that uses it.

- **Check for accidental loops.** A workflow that triggers a refetch which triggers another workflow can quietly burn bandwidth.

---

<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:** [May 4, 2026, 6:48pm UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/8 "2026-05-04T18:48:28Z")

</div>

> [@Slavo](#):
>
> **Xano API responses** - every workflow call returns JSON, and JSON adds up fast if you’re returning whole records when you only need a few fields, or fetching long lists without pagination.

How does anything in the Network tab (unless routed through WeWeb’s servers) have to do with WeWeb’s bandwidth? Client-side requests are .. client-side – unless I’m missing something.

So it would make sense for **Xano usage/bandwidth/rate limits** , but it should **not normally count as WeWeb-hosted bandwidth** unless WeWeb is proxying the request or serving/caching the response through its infrastructure.

It’s hard to believe “they add up” if WeWeb mostly calls them client-side.

---

<div class="post-metadata">

**Author:** ![Slavo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/slavo/32/13253_2.png) [@Slavo](https://community.weweb.io/u/Slavo)\
**Post date:** [May 6, 2026, 4:58am UTC](https://community.weweb.io/t/bandwidth-how-does-that-work/21121/9 "2026-05-06T04:58:52Z")

</div>

CDN traffic is part of “Bandwidth”
