Services
Project auditDevelopment from scratchRefactoringREST APIUI componentsSEO & content
Case studiesAboutContactDiscuss a project
Home/Services/Project audit
Service · flagship

Vue / Nuxt audit — find out exactly what's slowing your project down

I go through the application across four layers — architecture, performance, reliability, SEO — and hand over a working document: what's broken, what's critical, in what order to fix it, and how long it'll take. Not a list of complaints — a plan of action.

Order an audit What's in the report
Who it's for

Is an audit your
next step?

Подходит

  • The team argues about performance instead of fixing it
  • You're onboarding a new contractor — you need an independent assessment
  • You're preparing to migrate from Vue 2 to Vue 3
  • You want to know where to invest resources first

Не подходит

  • You need a specific bug fix, not a systemic assessment
  • You want to "confirm everything is fine" — an audit will find what it finds
  • The project is a one-off and won't be developed further
01 — When you need one

Something's off — but what exactly?

An audit isn't "fix a bug." It's an independent look at the whole project: what's good, what's critical, what it risks for the business. Honest, no sugarcoating.

!

The app is slow — the team argues about causes instead of fixing them.

!

The bundle is pushing 5 MB, CWV is red, rankings are dropping.

!

The code was inherited: every commit is a gamble.

!

You need an independent assessment — hiring a team or handing off the project.

02 — What I check

Four layers
of the application.

Each layer is a separate section of the report, with findings, code examples, and an assessment of business impact.

L1

Architecture

Structure, separation of concerns, state management, reusability, module coupling.

structurestatecoupling
L2

Performance

Bundle size, code-splitting, lazy-loading, dependencies, rendering strategy, Core Web Vitals.

bundleCWVrender
L3

Reliability and code

TypeScript typing, error handling, tests, readability, duplication and tech debt.

TypeScripttestserrors
L4

Security and SEO

Frontend vulnerabilities, SSR/SSG, indexability, Schema.org markup, meta tags.

SSR/SSGa11yschema
03 — What you get

A report you can
actually act on.

Not a list of complaints, but a working document: what's good, what's critical, in what order to fix it, and how long it takes. Six sections in the PDF.

  1. 01
    Executive summary

    No jargon: what's good, what's critical, what it risks for the business. A page you can show the client.

  2. 02
    Problem map

    Every finding comes with its layer, exact location in the code, and snippets. Nothing unsubstantiated.

  3. 03
    Prioritization

    Critical / important / nice-to-have — with an assessment of impact on the business and users.

  4. 04
    Recommendations

    Concrete steps for every problem. Not "needs optimizing" — exactly what to do.

  5. 05
    Roadmap

    Order of work and effort estimates — so you can plan sprints and budget.

  6. 06
    "Before" metrics

    CWV and bundle size are recorded — so you'll have something to compare the result against after the fixes.

04 — How the work goes

Transparent,
step by step.

01

Access and context

You give access to the repository and describe the pain points. If there's an NDA, we sign it before starting.

~ 1–2 hrs
02

Layer-by-layer review

I go through the four layers, recording findings with code examples and metrics.

3–5 business days
03

Report and call

I hand over the PDF and walk through it on a call — answering the team's questions.

~ 1–2 hrs
04

Optional — fixes

I can take on implementing the plan, or hand it off to your team.

by agreement

A basic audit takes from 5 business days in total.

05 — Why me

I look at code
as an engineer
and as a designer.

  • ✓
    8 years in a demanding domain. Airline booking systems — one of the most demanding domains in frontend.
  • ✓
    Open source as proof. I publish reusable, accessible packages — the code can be read.
  • ✓
    A design foundation. I see not just the architecture, but how it'll feel for the user.
  • ✓
    Honesty about timelines. An estimate before we start. No vague wording and no surprises at the end.
06 — Вопросы

FAQ

Yes, the audit is done on the source code — that's what lets me find the real causes, not just symptoms. If there are restrictions, we'll work out a format: read-only access, a separate branch, or work on your side.
A basic audit takes from 5 business days. The exact timeline depends on the size and depth of the codebase: a large application with legacy code may need more time. I fix the timeline before we start.
If you'd like. The report is self-sufficient — your team can implement it. But I'm also ready to implement the plan myself: then "before/after" metrics settle the question of results.
Yes. Besides auditing the current state, these projects often benefit from a section on migration strategy to current versions — with an assessment of risks and effort.
Standard situation. We sign an NDA before I get access, and project materials stay confidential. In public case studies I only publish what I have permission to.

Related services

/refactor

Refactoring

I clean up existing code — architecture, TypeScript, migration to Vue 3.

/seo

SEO & content

I make the app indexable and fast, and write on-topic content.

Example of my work

TravelShop — an audit on a live project.

Airline bookingVue 3 · NuxtSSR

Worked on the ORS team on TravelShop — a flight search and booking system. As part of the project I audited the codebase: identified bottlenecks in architecture and performance, implemented REST API caching, and improved the reliability of key flows.

Read the case study →
Next step

Find out what shape your Vue project is really in.

Describe your stack and what's hurting. I'll tell you how long the audit will take and how much it costs. The first review is free, no obligations.

Order an audit Other services