Audit / Decision
KNOW WHAT TO FIX BEFORE YOU REBUILD.
When a site has several symptoms at once—slow pages, broken updates, SEO uncertainty, plugin conflicts or an unclear architecture—the highest-value first step may be diagnosis rather than another isolated fix.
SCOPE / DELIVERY
WHAT THE WORK COVERS.
The audit is bounded before it starts. Evidence is collected against agreed symptoms and environments, then translated into decisions the business can actually sequence.
Architecture and dependency map
Map architecture, hosting, themes, plugins, integrations and ownership so the technical surface is understood before individual findings are judged.
Performance and front-end review
Measure representative pages and workflows across performance, front-end behaviour, validation, search foundations and maintainability.
SEO/accessibility foundations
Trace visible symptoms back to likely causes, dependencies and reproduction steps instead of returning a list of automated warnings.
Prioritized remediation plan
Prioritise keep/configure/refactor/replace/rebuild actions by impact, effort, risk and the consequences of leaving the issue unresolved.
FAQ / DECISION
Questions, answered.
What do I receive at the end of the audit?
A bounded set of evidence, prioritised findings and a recommended implementation route—not an unfiltered export from automated tools.
Is an audit useful if I already know the site needs work?
Yes when the uncertainty is about sequence and scope. It can prevent paying to optimize a layer that should be replaced or rebuilding parts that are still valuable.
Deliverable
The output should support a decision, not create a thicker report.
The audit concludes with prioritised actions: keep, configure, refactor, replace or rebuild. Each recommendation is tied to impact, effort, dependencies and the risks of leaving the problem unchanged.
The report is not the product; the decision is. A useful audit makes it clear which issues are urgent, which are structural, which can wait and where further work would have poor return.
- 01
Executive summary in plain languageExplain the system, main risks and decision in language a business owner can act on.
- 02
Evidence and reproduction stepsKeep enough evidence to reproduce important findings instead of relying on screenshots of scores.
- 03
Priorities by impact and effortSeparate high-impact structural work from quick fixes and low-value noise.
- 04
Recommended implementation routeEnd with a realistic route: configure, refactor, replace, rebuild or leave alone.
Project workflow
Audit to implementation
The audit is deliberately bounded. Scope and evidence are agreed first so the output answers a decision instead of becoming an endless exploration of everything that could be improved.
-
Define the scope
Agree which symptoms, pages, workflows and environments are included.
-
Measure
Collect repeatable evidence rather than relying on a single automated score.
-
Trace
Identify the technical and organisational causes behind the visible problems.
-
Prioritise
Separate quick wins, structural work and low-value distractions.
Questions answered
Questions clients usually ask
Is an audit useful before a complete redesign?
Yes. It identifies content, URLs, integrations and technical risks that need to be preserved or deliberately replaced during the rebuild.
Can you audit a plugin or custom codebase?
Yes, when the scope and access make a meaningful review possible. The audit can focus on architecture, WordPress integration, dependencies, failure modes and maintainability.
Will you fix the issues you find?
That can be included as a separate implementation phase. Keeping audit and implementation decisions explicit helps the business understand the work rather than receiving an open-ended maintenance invoice.
Can you guarantee that every problem will be found?
No audit can guarantee discovery of every latent issue. The scope, environments, evidence and limitations are stated clearly so the findings can be interpreted responsibly.
NEXT / COMMERCIAL
BRING THE REAL PROBLEM
START THERE.
If the site has several problems and every proposed fix seems to create another question, send the URL, symptoms and the decision you are trying to make. The audit should reduce uncertainty before implementation starts.
DISCUSS A PROJECT