Emery Studio.Start an audit
Technical UX Audit

Stop guessing. Get a roadmap in a week.

A fixed-scope review of your site and the frontend underneath it, starting at $1,500. You get a ranked list of what to fix, improve, rebuild, or leave alone.

Start with an audit

What I look at

  • UX friction
  • Performance
  • Accessibility
  • Frontend bloat
  • Forms and conversion paths
  • Tracking clarity
  • Search and structure
  • Fix vs rebuild decisions
Start here

Technical UX Audit

Starting at $1,5001 week, fixed scope
  • Priority-ranked reportIncluded
  • Recorded walkthroughIncluded
  • Quick wins listIncluded
  • Implementation notesIncluded
  • Next-step roadmapIncluded
Start with an audit
Example report preview

Separate the urgent fixes from the noise.

The point isn't a terrifying list of everything wrong. It's making the next move obvious.

workwithemery.com / your-site

Frontend health snapshot

Speed

48

CLS

Needs work

A11y

72

UX clarity

58

Sample findings

  • HighUXPrimary action is unclear on mobile.
  • MediumSpeedThird-party scripts delay the first useful view.
  • MediumA11yForm errors aren't announced to assistive tech.
  • LowSearchStructured data is missing on service pages.

Sample figures, shown to illustrate the format. Your report uses your real numbers.

Questions

Answers before you ask.

What does the audit cost?

The Technical UX Audit starts at $1,500, fixed scope, delivered in about a week. You know the price before we start.

What happens during the audit week?

I go through the customer experience and the frontend underneath it: UX friction, performance, accessibility, tracking, and the fix-versus-rebuild calls. You get a recorded walkthrough so nothing gets lost in translation.

What do I get at the end?

A priority-ranked report, a quick-wins list, implementation notes, and a next-step roadmap. The goal is to make your next move obvious, not to hand you a pile of jargon.

What if I actually do need a rebuild?

Then I'll tell you, with the reasons. The point is to make that an informed decision instead of an expensive guess. Often the answer is “not yet,” and we fix what matters first.

Do you work with my stack?

Probably. I’ve worked across PHP, Laravel, WordPress, Shopify, React, Vue, and more. The stack is rarely the whole problem, so I focus on what’s actually getting in the way.

What happens after the audit?

If you want the fixes done, I can do them: an improvement sprint, a scoped build, or ongoing support. No retainer required to get the audit, and no pressure after it.

Who actually does the work?

I do. You work directly with me, start to finish. No account managers, no handoffs, no junior team learning on your project.