QA: Review frontend bundle size / loading speed (post-motion)

PlasticDigits commented

2026-03-28 09:43:56 +00:00

(Migrated from gitlab.com)

Summary

Please have QA dev @brouie assess whether frontend bundle loading speed is acceptable in realistic conditions (cold load, repeat visit with cache, throttled network if available).

Context

We added motion for route transitions and richer interactions. Production builds now report a large main chunk (~1 MB+ minified) and Rollup suggests considering code-splitting / manualChunks.

Ask

Measure or subjectively evaluate time-to-interactive / perceived load for the Vite production build (e.g. npm run build && npm run preview).
Confirm whether the current bundle behavior is acceptable for our target users and hosting.

Resolution rules

If loading is acceptable: close this issue (optionally note metrics or “LGTM” in a comment).
If not acceptable: leave this issue open until a fix is implemented (e.g. lazy routes, manual chunks, or other agreed bundle strategy), then close with a short summary of what changed.

frontend/ — Vite build, motion dependency
CI / preview: npm run build, npm run preview

## Summary Please have **QA dev @brouie** assess whether **frontend bundle loading speed** is acceptable in realistic conditions (cold load, repeat visit with cache, throttled network if available). ## Context We added `motion` for route transitions and richer interactions. Production builds now report a **large main chunk** (~1 MB+ minified) and Rollup suggests considering code-splitting / `manualChunks`. ## Ask 1. Measure or subjectively evaluate **time-to-interactive** / perceived load for the Vite production build (e.g. `npm run build && npm run preview`). 2. Confirm whether the current bundle behavior is **acceptable** for our target users and hosting. ## Resolution rules - If loading is **acceptable**: close this issue (optionally note metrics or “LGTM” in a comment). - If **not acceptable**: **leave this issue open** until a fix is implemented (e.g. lazy routes, manual chunks, or other agreed bundle strategy), then close with a short summary of what changed. ## Related paths - `frontend/` — Vite build, `motion` dependency - CI / preview: `npm run build`, `npm run preview`

PlasticDigits commented

2026-03-28 09:44:00 +00:00

(Migrated from gitlab.com)

assigned to @Brouie

Brouie commented

2026-04-21 04:14:10 +00:00

(Migrated from gitlab.com)

@PlasticDigits verified on 52b7f04.

Build metrics (production, npm run build):

Main: 1,023.87 kB min / 321.51 kB gzip
TimeCurvePage chunk: 486.34 kB min / 146.24 kB gzip
Total build: 11.25s
Rollup manualChunks/code-splitting warning present but not blocking

Combined gzip for main + TimeCurve = ~468 kB. Acceptable for the target audience (crypto users on broadband/LTE). Preview build renders TimeCurve page with all surfaces (timer, live buys, podiums, WarBow, modals) loading without perceptible delay. LGTM for current phase — revisit if/when we target lower-bandwidth markets or add heavier routes.

Clear for sign-off on #2.

@PlasticDigits verified on 52b7f04. Build metrics (production, `npm run build`): - Main: 1,023.87 kB min / 321.51 kB gzip - TimeCurvePage chunk: 486.34 kB min / 146.24 kB gzip - Total build: 11.25s - Rollup manualChunks/code-splitting warning present but not blocking Combined gzip for main + TimeCurve = ~468 kB. Acceptable for the target audience (crypto users on broadband/LTE). Preview build renders TimeCurve page with all surfaces (timer, live buys, podiums, WarBow, modals) loading without perceptible delay. LGTM for current phase — revisit if/when we target lower-bandwidth markets or add heavier routes. Clear for sign-off on #2.

Brouie (Migrated from gitlab.com) closed this issue

2026-04-21 04:14:25 +00:00

PlasticDigits commented

2026-04-22 06:49:56 +00:00

(Migrated from gitlab.com)