Complete audit.

The complete audit is the visual audit and the white box backend audit together, plus a performance workstream that goes well past a Lighthouse score. Take it when you already know the store is slow and need to know precisely why, or before a replatform, an acquisition or a new head of ecommerce. It is quoted before it starts, once I know how many templates and systems are involved.

PricedQuoted

Quoted before it starts, fixed once agreed
Read-only admin, repository and server
A call to walk you through it

AI-generated

HighDatabase

Slowest template, slowest query

HighDelivery

Images sent at desktop size to phones

MediumHosting

Cache cleared on every stock update

Example findings

Read in order: each audit takes more access than the one before it. All prices exclude VAT.

What it delivers

Everything, plus the performance work

What it covers

Everything in the visual audit and the white box backend audit: every template, the accounts, the code, hosting and database
The code read line by line, every module and plugin checked, and the code-level security scans
Lighthouse per page template, on a laptop and a phone
Request waterfalls: what blocks the page, and for how long
Server response by template, and caching at the edge and the origin
Image weight, formats and how they are delivered
The database queries behind the slowest templates
Core Web Vitals field data, where Google holds it for you
A ranked list of what is costing the most milliseconds

What it does not

Doing the work: it tells you what is slow, why, and the order to deal with it
Write access to anything: every login is read-only
How the business runs behind the site: that is the workflow audit
Any change to the live store: nothing is edited, installed or switched on
Re-testing once the fixes are made, which is quoted with the work

What arrives

A document you can plan a year from

One document in six parts, with a page per finding: what it is, what it is costing you, how to fix it, how long the fix takes and what it costs to resolve. It reads as easily to a finance director as to a developer.

Reports usually run to 100 to 150 pages. The longest so far was 350, for a Magento 1 store with 59 plugins, half of them custom. Every section opens with a summary, so it can be read in parts. The visual report is sent separately, password protected, through a link that works once.

How the audit was done: scope, method and how every number was produced
The store scored across nine areas, from measured evidence
The measured position, template by template
Every finding ranked by severity and what it costs
The store against two competitors crawled the same day
What I would do, in what order, and the assumptions that order rests on

Still an audit. It tells you what is slow, why, and the order to deal with it. Doing the work is a separate engagement, quoted once you have the report.

From a real full audit

Twenty-three findings, ranked

Every finding in a full audit is ranked by severity and by what it costs, so the first pages say where to start. This is how one recent report split.

23findings, one report

Critical, a customer cannot finish, or it is costing sales now3 · 13%
Major, costing sales or trust every day11 · 48%
Minor, worth fixing in the same pass8 · 35%
Cosmetic, noticed, not urgent1 · 4%

Method · Counted from a full audit for a UK retailer with a catalogue of several thousand products, issued September 2026. The client is not named.

110sites

Measured

audited, every finding recorded where and when it was seen.

Method · Audits run, not sites visited. The habit comes from training in digital forensics.