Technical audit
Website technical audit: written findings in five business days.
One fixed fee, taken off the build price if you build with us. We examine your existing website or web app (architecture, speed, search, security, releases and ownership) and hand you ranked findings and a roadmap any developer can follow.
01 — Price and what you receive
Technical audit: fixed scope, fixed price.
Scope and fee are fixed before we start. You receive ranked findings, the evidence for each, and a roadmap ordered by what to fix first.
12,000 EGPFixed price
You build it with us
If you go on to build with Altruvex, the 12,000 EGP comes off the project price.
You build it elsewhere, or not at all
If you don't, you keep the findings and the roadmap — the fee stands.
What is included
- Architecture: rebuild or repair
- Performance, including Core Web Vitals
- Security surface
- Search and data: SEO, structured data, analytics
- Releases: build pipeline, environments, backups
- Ownership: repository, accounts, licences, documentation
- A written roadmap and a 1-hour debrief call
02 — Why audit first
Check the decision before you pay to build it.
Changing a decision is cheap while it is on paper and expensive once the site is live. The audit is one fixed fee, paid once, before you commit to a build.
12,000 EGP, before you commit to any of 22,000 – 275,000 EGP — and it comes back off the build if you go ahead.
- Caught by the audit 12,000 EGP · 5 business days · credited to the build
- Found after launch
- What the audit spares you
- 12,000 EGP
- Fixed. The audit is quoted, never estimated.
- 5 business days
- From the day access and context arrive.
- 22,000 – 275,000 EGP
- The published build range the decision stands in front of.
- Nothing
- Net cost, if you go on to build it with us.
Only the fee, the five-day window and the build range are real figures; they come from our published prices. The curve has no numbers on its vertical axis because we have not measured your system yet.
03 — What the audit answers
Six questions. Six written answers.
Six areas, each with the question it answers, what we examine and what you receive in writing. The report is yours whether you build with us or not.
Architecture
Do we rebuild, or repair what we have?
What we look at: Current stack, hosting and deployment flow · Service and data ownership boundaries · Framework and platform lock-in · How it connects to other systems
What comes back
- A map of the system as it behaves, not as it was designed
- A rebuild-or-repair recommendation with the tradeoffs written down
Performance
Why is it slow — and which fix is worth paying for?
What we look at: Core Web Vitals measured on real devices · Server response time and cache strategy · Page weight and third-party scripts · Image and font delivery
What comes back
- Ranked bottlenecks with the measurement beside each one
- The subset worth fixing, and the subset that is not
Security
Where could someone get in today?
What we look at: Authentication and session handling · Exposed surface and secret handling · Dependency vulnerabilities · Access and permission model
What comes back
- A surface assessment with severity per item
- A remediation order that does not require a rewrite to start
Search & data
Why can’t search see what we publish?
What we look at: Indexability and the rendering path · Structured data and metadata coverage · Analytics and event integrity · Content model and migration risk
What comes back
- What is invisible to search, and why
- A content-model verdict before migration, not after
Releases
Can your team release updates safely?
What we look at: Build pipeline and rollback path · Whether test and live environments match · Backup and restore, actually tested · Release cadence, and who is blocked by whom
What comes back
- The gap between what CI claims and what shipped
- A delivery path your team can run without us
Ownership
Do we own this system, or rent it?
What we look at: Repository, domain and account control · Licences and third-party terms · Documentation and handover state · Whether one person holds the only knowledge
What comes back
- A written answer to who owns what
- Whatever is missing to take the system elsewhere
These are the questions the scope answers, not answers about your system. Those are written only after we have looked.
04 — Who it is for
A system that exists, and a decision that does not.
The audit is for a website or application that is already built, or half-built, and a question about what to do with it next.
A fit when
You need an outside read before you spend.
- You are weighing a rebuild against repairing what you have.
- The site is slow, or search does not see what you publish.
- You inherited a codebase and need to know what you actually own.
- You want written findings before you commit to any build range.
Not a fit when
Another route answers it faster.
- Nothing is built yet. Start with the initial project consultation call and a proposal.
- A live site needs one urgent fix. That is change work, quoted before it starts.
- You need a formal penetration test or a compliance certificate. The security channel reviews the surface; it does not certify it.
05 — How the audit runs
Access in, written answers out.
The window is five business days, counted from the day access and context arrive.
- 01 — Access
You grant read access and tell us what prompted the audit. The five days start when both have arrived.
Your part: Repository, hosting and analytics access, and the question you most need answered.
- 02 — Examination
We work through the six channels above against your actual system: measured, not assumed.
Your part: Answer questions as they come up. Nothing else.
- 03 — Findings
Findings ranked by risk, the evidence beside each one, and a roadmap ordered by what to fix first.
Your part: Read them before the debrief, and note what is unclear.
- 04 — Debrief
A call to walk through the findings and the roadmap, and to answer what the document cannot.
Your part: Bring the people who will act on it.
- 05 — Decision
The roadmap is yours to run with us, with your team or with another developer. If you build with us, 12,000 EGP comes off the build.
Your part: Decide what happens next.
06 — Terms
The terms, fixed before we start.
Scope, fee and window are agreed in writing before access is granted. Nothing here is estimated.
Fee
One fixed fee, paid once.
- 12,000 EGP, fixed before we start
- Quoted, never estimated or billed by the hour
- The findings and the roadmap are yours once delivered
Window
Five business days.
- Counted from the day access and context arrive
- A system with several codebases or integrations is scoped separately before we start
Credit
The full audit fee is credited toward a subsequent build.
- 12,000 EGP comes off the project price when you build with us
- If you build elsewhere, or not at all, the findings and roadmap stay yours
Not the consultation call
A paid service, not the free call.
- The 30-minute initial project consultation call is free and separate
- Book the call when nothing is built yet; start with the audit when a system exists
Start with the technical audit when the problem is unclear, the system already exists, or more than one build path is possible. Start with development when the scope, architecture and success criteria are already defined.
12,000 EGP, fixed before we start. If you go on to build with us, 12,000 EGP comes off the project price.
No. The consultation call settles whether there is a fit and what the next step is. The technical audit is a paid, fixed-scope service: we examine your system and return written findings and a roadmap.
The audit covers six areas: architecture, performance (including Core Web Vitals), security, search and data (SEO implementation, structured data and analytics), releases (build pipeline, environments and backups) and ownership (repository, accounts, licences and documentation).
Yes. The audit is designed to produce a roadmap that can be implemented by Altruvex, your internal team, or another developer — you keep the findings and recommendations either way. If you do go on to build with us, we credit 12,000 EGP against the project price; if you don't, the fee stands and the roadmap is still yours.
Five business days, counted from the day access and context arrive. A system with several codebases or integrations is scoped separately before we start.
Read access to the repository, hosting and analytics, and a short note on what prompted the audit. The five business days start once both arrive. Without code access, performance and search can still be measured from the live site, but architecture, security and delivery findings need the code.
Next step
Send the site. Get written answers in five business days.
Send the site or system and what prompted the question. If the audit is the wrong tool, the consultation call will say so.