The product is slowing down
Important screens take longer to load or respond. We look at the frontend causes and which improvements are worth making first.
FRONTEND RISK AUDIT
A focused review of your frontend: what is working well, what may cause problems, and what to improve next. We agree the scope and fixed fee before work starts.
Important screens take longer to load or respond. We look at the frontend causes and which improvements are worth making first.
Small changes cause regressions. You want to understand what makes the frontend fragile and how to make the next changes more predictable.
Your product has users or paying customers. You want an independent frontend review and practical advice, explained without assuming you are a developer.
You are bringing in a developer, changing teams, or taking over an existing product. You need to understand the frontend before deciding what to change.
WHAT YOU RECEIVE
Your priorities, with supporting evidence and an explanation of the impact on the product.
A readable explanation, recommendations, review limitations, and a record of the risks identified.
A practical order of work: what to fix first, what can wait, and what to leave unchanged.
An optional 30-minute Q&A is included to discuss the report.
We review how the frontend is built, how important user journeys perform, and how changes are made. The specific focus is agreed around your product.
Implementation is discussed separately. The audit is not an exhaustive review of every line, a full security audit, or an accessibility certification.
If access is limited, we agree what can be verified before confirming the proposal.
STARTING PRICE
Excl. VAT. Companies with a Portuguese company NIPC: from €1,500 excl. VAT.
The final scope and fee depend on complexity and are agreed before the audit starts.
REVIEW TIME
Once the agreement is signed, the agreed payment is complete, and we have all required materials. We confirm the start and delivery dates with you.
Most communication happens in writing.
AUDIT QUESTIONS
Reviewing the code requires repository access and relevant context. Specific access is agreed and requested after the contractual stage.
You can use it yourself or share it with a developer. We explain the findings in plain language and identify changes that need technical help. Implementation is discussed separately.
Before access is shared, we agree what can be reviewed, who can access it, and how the information may be used.
Describe the product, the concern, and any deadlines. We’ll reply about fit and availability.
Request audit availability