Check journeys
Forms, purchases, search and access—not just the appearance of the homepage.
BIG FISH / Technical website audit
Technical website audit
Assess a website before maintenance or a substantial change. Connect technical findings to their effect on visitors and the business, and turn the result into a practical work plan.
Based on audit scope · scoped around your project
Enquiry / delivery route
Form: success?
01Form: success?
02Delivery investigation
03Cause identified
Fictional data. No production systems are connected.
SUPPORT × DESIGN × DEVELOPMENT
A familiar team.
The next stage of your product.
Collect evidence
Record reproduction conditions, impact and how each correction will be verified.
Set priorities
Separate critical faults, technical debt and improvements that can be scheduled.
EXPLORE THE JOURNEY
From an observation
to a prioritized task.
Switch options to see how the solution changes. This demonstrates the approach using fictional data.
01 / Technical website audit
Observation
A form reports success, but the client team receives no enquiry. Reproduce the journey.
How the work is estimated ↘Enquiry / delivery route
Form: success?
01Form: success?
02Delivery investigation
03Cause identified
Fictional data. No production systems are connected.
02 / Technical website audit
Cause
Check storage, delivery logs and the CRM response. Identify where the enquiry is lost.
How the work is estimated ↘Enquiry / delivery route
Delivery investigation
✓Form: success?
02Delivery investigation
03Cause identified
Fictional data. No production systems are connected.
Check passed. The next stage can be approved.
03 / Technical website audit
Plan
Specify the fix, owner and acceptance criteria. Repeat the test after implementation.
How the work is estimated ↘Enquiry / delivery route
Cause identified
✓Form: success?
✓Delivery investigation
03Cause identified
Fictional data. No production systems are connected.
A CLEAR PROCESS
See the result.
At every stage.
- 01
Audit brief
Define questions and review boundaries.
- 02
Evidence
Inspect journeys, environments and available code.
- 03
Findings
Confirm issues and assess impact.
- 04
Action plan
Deliver priorities and criteria for verifying fixes.
SCOPE AND PRICING
The support
your product needs.
Audit pricing depends on the number of journeys, source-code access and review depth. Implementing recommendations is estimated separately.
Technical website auditBased on audit scope
A precise quote follows a discussion of your project.
DOCUMENTATION
Project knowledge.
Stays with you.
Document coverage follows the agreed task. Secrets are stored separately from shared instructions.
Project record
Environments, versions, services, owners and access-management rules.
Release procedure
Pre- and post-release checks, backup and recovery conditions.
Change log
What changed, when it was released and how to verify it.
Team instructions
Content editing and new features without editing source code.
IN DETAIL / 01
Scope of the review
Agree the purpose first: onboarding to support, fault investigation, performance review or a development plan. Record available environments and limitations. An external review and source-code analysis provide different depths of evidence.
Load tests and potentially destructive checks require agreed conditions. An audit does not automatically authorize production changes or test payments.
IN DETAIL / 02
User journeys
Follow key desktop and mobile routes: find information, submit a form, sign in or order. Check validation, failure states and confirmation.
A successful screen does not prove an enquiry was delivered. Where the relevant systems are accessible, verify storage and downstream transfer. Describe reproduction steps, actual behaviour and expected behaviour for each defect.
IN DETAIL / 03
Technical condition
Review dependencies, errors, cache settings, backups and access rules. Investigate performance in stages: server response, resource loading and readiness for interaction.
Technical search checks cover URL status, redirects, canonical links, indexing and the sitemap. They do not replace an SEO strategy or demand research, but can reveal barriers to crawling and understanding pages.
IN DETAIL / 04
An actionable report
Findings become tasks with evidence, impact and priority. Confirmed defects are separated from hypotheses needing further investigation. Implementation is estimated once its scope is clear.
The client receives a sequence of work: what to fix first, what can share a release and what can wait. Agreed checks are repeated after corrections. An audit itself does not change the code; implementation is a separate stage.
FAQ
Before we start.
Do you only support your own projects?
Our main approach is to continue developing products we built. Projects from other teams are reviewed first: code, access and risks determine whether ongoing support is feasible.
Do we need a monthly subscription?
No. Individual tasks can be agreed separately. Ongoing support suits a regular stream of changes and a planned backlog. Use and rollover of hours are defined in the contract.
How quickly will you fix an error?
We first identify impact and cause. Response times, working hours and urgent contact arrangements are agreed separately. Resolution time depends on the fault and external services.
What do we receive?
A verified outcome, change description and report for the agreed scope. New functionality comes with updated instructions. Documentation depends on the task.
BIG FISH / MAINTENANCE
Find the right solution
for your project.
NEXT STEP
Understand what holds
your website back.
Tell us what you want to change or which problem to solve. We will start with the task and propose a suitable way to work.