Skip to main content
Varanity/

Numbers, not adjectives.

The commitment

We measure every engagement before it begins and again at delivery — using Lighthouse CI on a throttled mobile profile against a production build, not a local dev server. The numbers on this page are recorded exactly — no rounding up, no “up to”, no “faster” without a unit attached. When client data is published here, it will show the before score, the after score, and the measurement method. Both numbers, not just the after.

Aggregate targets

What every build has to clear.

01
Target LCP
< 2.5s

Largest Contentful Paint.

The hero block of every page has to render in under 2.5 seconds on a mid-tier Android device, on a real mobile 4G profile. Not on a developer's laptop. Not on synthetic Lighthouse. On the device a customer actually holds.

StandardGoogle CWV "good" threshold · enforced at deploy time
02
Target INP
< 200ms

Interaction to Next Paint.

When a visitor taps a button or submits a form, the page responds in under a fifth of a second. Slow input response drives visitors to close the tab. We strip render-blocking JavaScript, defer third-party tags, and audit every interaction on every build.

StandardGoogle CWV "good" threshold · all 75th-percentile inputs
03
Target CLS
< 0.1

Cumulative Layout Shift.

The page does not move under the visitor's thumb. Image and media slots have reserved dimensions. Fonts are pre-declared. Skeletons match their loaded counterparts. The shift score stays inside the good range.

StandardGoogle CWV "good" threshold · 75th-percentile
04
Lighthouse Performance
90+

Composite score, mobile.

Every deploy runs against a production-equivalent Lighthouse profile. A score below 90 fails the build and the deploy is blocked. There is no "we'll get it next sprint" path.

StandardCI gate · main branch · mobile profile · throttled
05
First Load JS
< 90KB

JavaScript sent to the browser.

The bundle shipped to a first-time visitor is capped at 90 kilobytes. On a mobile network where data costs money, every kilobyte of JavaScript is a cost your visitor pays before they see your content. We measure this per route and block deploys that exceed the cap.

StandardNext.js bundle analysis · CI gate · marketing page routes
06
Critical a11y violations
0

WCAG 2.2 AA at delivery.

Every build runs an accessibility audit against all public routes. Zero critical violations is the gate — not a target, not a best-effort. An accessible site is also a site that performs on screen readers, assistive technology, and low-vision browser configurations.

Standardaxe-core · CI gate · WCAG 2.2 AA profile
Engineering targets, gated at deploy time. Aggregate client medians replace these figures as engagements complete. Publication requires explicit client consent — that consent form is part of every project close-out, not an afterthought.Check this site's scores ↗Last revised · 2026 Q2
How we publish proof

Every engagement begins with a baseline and ends with a measured delta.

We measure your site before we touch it — on the device profile your customers actually use — and we measure it again the day we hand it back. The two numbers, side by side, are what goes here.

Until then, this page carries the targets we hold ourselves to. We would rather an empty grid than a fabricated one — and we would rather earn the first entry on it than borrow somebody else’s.

See the auditEvery case study
begins this way
Method · four steps
01

Baseline before kickoff.

LCP, INP, CLS, TTFB and conversion-path metrics captured on the live site before a single line is changed. Real user monitoring, not synthetic.

02

Budget at every commit.

A performance budget is enforced in CI. A regression on any tracked metric fails the build. The budget is published in the engagement contract.

03

Re-measure on deploy.

Same instruments, same network profile, same hardware class. The delta is computed against the baseline — not against a freshly-launched marketing claim.

04

Publish with permission.

Before/after numbers go on this page, with the client's written consent, exactly as measured. Adjectives don't appear. If a number didn't move, we say so.

Let's talk

Tell us what your site needs to do.

Start with a conversation — no pitch, no obligation. We'll tell you honestly whether we're the right fit, and where we'd start.