Triqodex
Start a project
Blog / Engineering

Performance budgets: making speed a requirement, not a hope

·4 min read·Triqodex Engineering

Every project we ship has a performance budget agreed at the start: maximum JavaScript per route, a target Largest Contentful Paint, and a ceiling for layout shift. The budget lives in the repository and is checked on every pull request.

What we budget

  • JavaScript shipped per route (compressed)
  • LCP under 2.0s on a mid-range phone over 4G
  • CLS under 0.05
  • Interaction to Next Paint under 200ms

When a change breaks the budget, the build fails, and the conversation happens in code review rather than after launch. Most of the time the fix is small: a lazy-loaded component, a smaller dependency, or a server component instead of a client one.

Speed compounds. Faster pages convert better, rank better and cost less to serve. Treating it as a requirement is the cheapest way to keep it.

Keep reading
SaaS
·7 min read

Multi-tenant SaaS: the architecture decisions you can't easily undo

Tenancy model, data isolation and billing boundaries are cheap to decide on day one and expensive to change on day 400. Here's how we approach them.

AI
·6 min read

AI agents in production: evaluation before autonomy

An agent that works in a demo and an agent that works on Monday morning are different systems. The difference is mostly evaluation.

Architecture
·5 min read

PostgreSQL or MongoDB? Start from the access pattern

The database debate is usually framed as relational versus document. The better question is how your application reads and writes data.

Start a project

Have a system worth building properly?

Tell us what you're working on. You'll talk directly with the engineers who would build it, not a sales team.

Start a project Explore our work