# Anime List optimization case study

> Canonical page: https://codevetter.com/benchmark/optimization/anime-list

A two-file import-boundary change materially reduced one local Vite navigation, while a separate production build showed almost no shipped-bundle movement.

## Result

- Decision: retained
- Observation date: 2026-08-14
- Primary metric: Local response bytes — 35.8% fewer
- Measurement note: 11,871,129 → 7,616,611 bytes
- Availability: Historical research receipt. The experimental browser harness is not part of the compact current release.

## Tested boundary

- Flow: One mobile home-page navigation in an isolated local Vite checkout
- Source: components/Navigation.tsx, components/ui/dropdown-menu.tsx
- Revision: db1faf0e0c27996c3eacfb9f1e3a4c0a65958938
- Correctness: One exact repository-owned Vitest test and the selected Playwright flow passed.
- Patch cost: 2 files, 62 gross changed lines, net 58, 0 production dependencies

## Decision path

- **Radix package subpaths (rejected):** 9.3% fewer bytes did not clear the 10% materiality floor.
- **Lucide removed from the initial flow boundary (retained):** 10 samples per side plus warmups confirmed the local transfer reduction.
- **Local developer-flow result only (qualified):** The production gzip change was 0.3%, so no consumer speed claim is made.

## Limitations

- The keep proves one local config-disabled Vite development navigation, not production traffic, representative devices, CDN behavior, or end-user impact.
- The correctness scope is one exact repository-owned recommendation test plus the selected Playwright flow; it is not the full Anime List suite.
- The production build check shows only a 0.313 percent gzip reduction, so this candidate should be presented as local developer-flow optimization rather than a consumer performance case study.
- The host agent still invents and applies source patches; CodeVetter owns evidence, boundaries, verification, decisions, and replanning.
- No production, cloud, registry, package installation, migration, deployment, paid-model, or secret operation was used.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)