Example engagement · High-traffic web app

Performance and quality gates in CI

A live web app failed Core Web Vitals on phones at peak traffic. We fixed the architecture behind it and added gates so it stays fixed.

This is an illustrative example of how we work, not a record of a client engagement or its results.

All examples

LCP, INP and CLS budgets on every pull request
In CI
reviewed at each release, by template and device
Field data
  • Astro
  • React
  • TypeScript
  • Vitest
  • Playwright
  • Jenkins

Context

Most users arrive on phones at peak times, when live data updates several times a second.

Challenge

The whole page rendered on the client, the bundle kept growing, and every live update re-rendered the main form, so taps lagged.

Approach

  1. Measured field data per template and device first, and wrote the targets into the spec as acceptance criteria.
  2. Moved the page shell to server rendering and hydrated only the live parts as islands.
  3. Batched WebSocket updates to one render per frame and isolated the main form from live re-renders.
  4. Added performance, accessibility and visual checks to CI, so a regression fails the build before it reaches users.

What changed

The key templates pass Core Web Vitals on phones, and the gates keep new features from undoing it.