1–2 weeks · fixed scope

Frontend audit

A frontend audit is a one-to-two-week, fixed-scope review of an existing frontend's privacy, security, accessibility and performance. Every finding is written as a spec delta, so it can go straight into a build, ours or yours.

What the audit covers

The audit reviews an existing frontend against five areas: the rules your product must follow, accessibility, performance, privacy leaks through third-party scripts and storage, and security headers and hygiene. We review the running site and the source code, so we see what users get and why.

Area What we check
Your rules Whether the interface does what your market rules require, against the rules your compliance team gives us
Accessibility WCAG 2.2 AA: keyboard paths, focus, contrast, labels, errors, motion, screen-reader output on key flows
Performance Core Web Vitals (LCP, INP, CLS) in lab conditions, and field data where it is available; bundle weight; render-blocking resources
Privacy Every third-party request and storage key, what loads before consent, and which form fields collect data without a stated purpose
Security Content Security Policy, HSTS and other headers; session and token handling; dependency vulnerabilities; secrets in the bundle

What you receive

You receive a findings report written as spec deltas: each finding states what the product must do, marked ADDED, MODIFIED or REMOVED, with the evidence and a risk rating. Because the findings are already in spec form, they can be estimated and built without being translated again.

Each finding includes:

  • The evidence. What we observed, where, and how to reproduce it.
  • The risk. How serious it is and who it affects, ranked so you can choose what to fix first.
  • The delta. The change to the spec, with an acceptance criterion in Given/When/Then that defines when it is fixed.
  • The check. How the fix can be verified automatically so the problem doesn’t return.

You also receive the inventory behind the privacy findings: every third-party request and every storage key, with what it does and whether the product needs it.

How the audit runs

The audit is fixed in scope and length, agreed before it starts. You know what will be reviewed, by when, and at what fee.

  1. Scope. We agree the URLs, flows and repository commit under review, and the rules to check against.
  2. Access. Read access to the repository and a staging environment, plus any rules or policies your compliance team holds.
  3. Review. Automated scans and manual review of the key flows, on the devices and browsers you support.
  4. Report. The findings report, ranked by risk, written as spec deltas.
  5. Walkthrough. A walkthrough of the findings in plain terms, with time for your team’s questions.

Why findings as spec deltas

Most audit reports end as a PDF that nobody turns into work. A finding written as a delta is already a requirement with a test. Your team, or ours, can estimate it, build it and prove it is fixed. It also leaves the product’s spec more complete than the audit found it.

What we don’t do

We review the frontend, its headers and what it sends to the browser. We don’t run penetration tests against your backend or infrastructure, and we don’t give legal advice on which rules apply to you. Where a finding depends on a legal reading, we say so and leave the decision to your compliance team.

After the audit

You keep the report and the inventory, whatever you decide next. Teams usually choose one of three paths:

  • Fix in-house. The deltas and criteria are written so your team can build and verify them.
  • Fix with us. The findings become the scope of a Build, estimated from the deltas.
  • Keep it fixed. A Retainer adds the checks to CI and keeps the spec current, so the same problems don’t return.

Pricing

The audit is fixed-fee, quoted after a first conversation once we know the size of the frontend and the flows in scope. It is invoiced in full on signature. We don’t publish prices.

Why an audit from us

Our own site makes no third-party requests and runs no trackers, and you can check that in your browser’s network panel before you message us. We hold client frontends to the same standard. For the checks we apply to every change, see the quality gates.

Start with an audit

One to two weeks, fixed scope. Findings arrive as spec changes, ready to build.

Ask about an audit