UX & Code Audit
A written review of how your product works and how it is built.
ServicesGaroon is a design and development studio in Yerevan, Armenia. We audit existing websites, apps and platforms from two sides: the interface, meaning how people move through it, and the code, meaning how it is built, how fast it loads and how safe it is. You get a written report and a prioritised plan, not a list of opinions.
In detail
Why one audit covers both design and code
Most problems a visitor feels are shared between design and engineering. A form that feels slow may be a heavy script, not a layout issue. A confusing menu may be the result of a database structure that nobody planned. If a designer reviews only the screens and a developer reviews only the repository, each misses half of the cause.
We are a studio that designs and builds, so the same team looks at both. That is the main reason to ask us. We can say not only that a checkout step loses people, but also whether the fix is a copy change, a different layout, or a change in how the page is built.
The audit is useful when a site has grown for years and nobody is sure what is on it, before a redesign so you do not repeat old mistakes, when a product is slow or visitors do not complete the main action, or when you take over a project from another team and need an honest picture of what you received.
What we look at
UX and interface: the main user journeys, such as finding a service, registering, calculating a price or placing an order. We go through them on desktop and phone, note every place where a person has to stop and think, and check navigation, labels, forms, error messages and the order of content. We also check consistency: whether buttons, spacing, type and components behave the same way across pages.
Content and structure: whether the page structure matches what visitors actually come for, whether headings say something, and whether the important facts are easy to find.
Code and infrastructure: the structure of the code, how pages are served, how heavy the pages are and what slows them down, the use of images and scripts, accessibility basics, security basics such as outdated components and exposed files, and how the site behaves for search engines. The exact scope is agreed per project. For larger systems we also review the architecture and how it connects to other services through APIs.
We look at what is there. If the project is under NDA or has parts we may not open, we agree the boundaries first and write them into the report.
How the audit goes
1. Brief and access. You tell us what worries you and what the site or product should achieve. We agree what we may see: the live site, a staging copy, analytics, and, for a code audit, the repository or a read-only export.
2. Walkthrough. We use the product as a new visitor would, on real devices, and record each problem with a screenshot and a short note.
3. Technical review. We check the code, hosting setup, performance and security, and connect findings to the screens where users feel them.
4. Prioritising. Every finding gets a severity and a rough effort: fix today, fix this month, or plan for the next redesign. This is the part that makes the report usable, because most teams cannot fix everything at once.
5. Report and call. You receive a written document and a presentation of it, in English. We walk your team through it and answer questions.
6. Optional next step. If you want, we carry out the fixes ourselves, hand the plan to your developers, or design a new version of the weakest parts.
What you receive
A written report with screenshots and clear descriptions, so people who were not on the call can follow it. A prioritised list of problems, each with what is wrong, why it matters and what to do about it. Short recommendations for design changes, with sketches where words are not enough. A technical section for your developers with specific, checkable items. And a plan that splits the work into quick fixes and larger changes.
We do not promise numbers such as a fixed rise in conversion. The report tells you what is blocking users and what is risky or slow, and which changes are worth making first.
What we have built for clients
An audit is more credible from a team that has built real products, so here is the work behind it. These are projects we designed and developed, not audits, and they show the kinds of products we know from the inside.
Arca, the national payment system of Armenia. We redesigned the corporate website so that banking partners, merchants and ordinary users can each find what they need in seconds, and so that long regulatory content stays readable. This is the kind of structure and content review we bring to an audit.
Cosmo Credit, a loan landing page inside the Idram&IDBank app. A loan page has to be quick to read and honest about cost, so we put the terms in a clear table and the repayment calculator in plain view. Checking that the cost of a product is visible and understandable is one of the first things we do in a financial audit.
Hashvich.am, an assistant for financial, tax and labour calculations. Many calculators with daily updated rules need a consistent interface and careful logic. We designed and developed it, so we know where such products tend to break.
Resync, a platform where researchers find collaborators. We designed the journey from short registration to a dashboard where search, matches and conversations sit together, and a system of cards that keeps dense profile data readable.
Soviem, a Shopify store for Soviet-era furniture and objects. We designed the whole shopping flow, from catalogue and collections to item pages and cart, and kept mobile on the same logic. Reviewing a shop means walking the same path a buyer takes.
Why Garoon
We have worked since 2018 on websites, interfaces and brands, in Armenia and abroad, mostly in fintech, e-commerce, hospitality and consumer goods. The people who write the audit have designed and shipped such products, so the recommendations come with an understanding of what they cost to implement.
We write plainly. A report should be read by a founder, a product manager and a developer, and each should understand their part of it.
We work remotely or in Yerevan, and we can continue after the audit if you want us to, or step away and leave you with a plan your own team can follow.
Selected projects
Questions clients ask
What is a UX and code audit?
It is an independent review of a live website, app or platform. We check how people move through it, how clear the interface is, and how the product is built: code quality, speed, security basics and structure. The result is a written report with findings sorted by importance, so your team knows what to fix first.
How is a UX audit different from a code audit?
A UX audit looks at what the user sees and does: journeys, navigation, forms, content and consistency. A code audit looks at what is under the surface: structure, performance, security and maintainability. Problems often cross over, so we usually do both and link each technical finding to the screen where users feel it.
What do you need from us to start?
A short description of your goals and worries, access to the live product, and, if you want the code reviewed, a repository or read-only export. Analytics access helps a lot. If some parts are confidential, we agree the limits at the start and write them into the report. Terms such as an NDA are agreed per project.
How long does an audit take?
It depends on the size of the product. A small marketing site is much quicker than a platform with many roles and integrations. After the first conversation and a look at access, we give a time estimate before any work starts. We do not give a fixed duration here because it would not be honest without knowing the product.
How much does it cost?
The price depends on the scope: how many journeys, how large the codebase, and whether you want only the report or help with fixes too. We name a fixed price for the audit after the first call and before we start. Send a short brief through the contact page and we will answer.
Do you fix the problems you find?
Only if you want us to. The report is written so that your own developers can follow it. If you prefer, we do the design and development ourselves, either as a set of quick fixes or as a redesign of the weakest parts. You are never obliged to continue with us.
Can you audit a product that someone else built?
Yes. You do not need to have built the site with us. What we can look at depends on the access you give us. We describe what we find without blame, because most issues come from years of changes made by different people under different deadlines.
Do you work with companies outside Armenia?
Yes. We work remotely with clients in Armenia and abroad, and meet in person in Yerevan when that helps. The audit is delivered as a document and a call, so location does not matter and no visit is needed. We write in English.
More services
Send us your request
Drop us a line
