Good first issue: reduce the frontend bundle size

Open

#4 opened on Sep 7, 2026 7 comments 0 reactions 1 assignee View on GitHub

@KavinamuthanGP is already working on this.

Since Sep 7, 2026.

Assessment

This issue has not been assessed yet.

good first issue help wanted performance

The production frontend build succeeds, but Vite reports that the main JavaScript bundle is larger than 500 kB after minification.

(!) Some chunks are larger than 500 kB after minification.

This is a good first issue for contributors who want to learn how the React/Vite frontend is organized.

Reduce the initial JavaScript bundle size by splitting code that is not needed for the first screen.

Inspect the Vite build output with a bundle visualizer or Vite's chunk reporting.
Consider lazy-loading page-level features such as the evaluation, improvement, asset-editor, or chat UI.
Consider separating large editor or visualization dependencies into dedicated chunks.
Keep the existing navigation and loading behavior usable while a lazily loaded page is fetched.

pnpm --filter agent-improvement-console-ui run build succeeds.
The initial bundle is materially smaller, or large dependencies are placed in clearly separated lazy-loaded chunks.
Navigation still works for every page.
No new console errors are introduced.
Add a short note to the PR explaining the chosen split points and the before/after build output.

pnpm --filter agent-improvement-console-ui run build
pnpm --filter agent-improvement-console-ui run lint

Questions are welcome—please comment on this issue before making a large architectural change.

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.