Homepage · Lighthouse mobile profile
Back to featured workOptimization in progress
Case study
Bunny Flow Studio
A public baseline turned into a prioritized optimization brief.
The problem
What the work needed to solve
The current public experience has a long mobile critical path. The job is to separate consequential bottlenecks from cosmetic audit noise, then improve the experience without overstating unfinished work.
Implementation
What I built or changed
- Captured a dated mobile Lighthouse baseline before changing the implementation.
- Mapped the 11.4-second LCP and 850 ms TBT to loading, rendering and JavaScript priorities.
- Separated accessibility repairs from performance work so both can be verified independently.
- Defined an after-audit gate: improvements will only be published after a new dated run exists.
Stack
Tools used in context
Evidence
Numbers with their context attached.
Every metric below names the page or test surface, profile, date and source. Limitations follow immediately after.
Homepage · Lighthouse mobile profile
Homepage · Lighthouse mobile profile
Homepage · Lighthouse mobile profile
Homepage · Lighthouse mobile profile
Homepage · Lighthouse mobile opportunity
Limitations
What this evidence does not prove
- This case study documents a current baseline, not a completed turnaround.
- Lab data is diagnostic; production impact must be checked with a dated after-audit and field data where available.
Next work
What comes after this snapshot
- Reduce the LCP resource chain and unused JavaScript before tuning secondary assets.
- Rerun the same mobile profile and publish a before/after comparison only if reproducible.