Diagnose
Technical UX audits, performance and accessibility reviews, and a clear, ranked list of what's costing you leads, speed, and trust.
Frontend product studio
You probably don't need a rebuild. You need to know what is actually getting in the way.
Most rebuilds start before anyone has diagnosed the real problem. Emery Studio finds what's slowing your pages, confusing your customers, and costing you leads, then fixes it. No agency overhead, no handoffs.
UX
where people get stuck
Speed
what's dragging pages down
A11y
what blocks real use
Build
what should exist next
How sites drift
The site worked when it launched. Then the business changed.
New plugins got added. Campaign sections stayed forever. Tracking scripts piled up. Templates got patched. Mobile flows drifted. Accessibility details slipped. A few rushed fixes turned into the way the site works.
- It still loads, but it feels slower and less stable than it should.
- The design still looks fine, but people don't know what to do next.
- The stack gets blamed, even when the real problem is how it was built and which product calls were made.
- Everyone knows something's off, but nobody knows whether to fix it, rebuild it, or leave it alone.
- That doesn't mean it's broken. It means the frontend needs to be understood before you spend on it.
Who this is for
This is for you if any of these sound familiar.
- You're weighing a rebuild and want to know if you actually need one.
- Leads or mobile conversions have slipped and nobody's sure why.
- The site feels slow or unstable, even though it still works.
- Your team keeps patching things and hoping nothing else breaks.
- You don't trust your tracking or analytics anymore.
- The design looks fine, but customers don't know what to do next.
You don't need all of these. One is usually enough to start with an audit.
How I help
Find what's getting in the way, fix what matters, and build what should come next.
You need senior frontend judgment, not a five-person agency and a six-week onboarding. Start with an audit, a focused improvement sprint, or a clearly scoped build.
No matter the platform
Your stack is rarely the whole problem. How it was built usually is.
PHPLaravelWordPressShopifyReactVueTailwindAnalytics
Rebuilding a PHP app in React won't fix unclear flows, slow assets, broken tracking, weak accessibility, inconsistent components, or product decisions that stopped matching how the business works.
Good products get built badly in modern tools every day. And good experiences can be recovered without throwing everything away. The work is figuring out what's happening, why it matters, and what to change first.
When the problem is unclear
Start with a Technical UX Audit.
One week, fixed scope. I review the customer experience and the frontend underneath it, then hand you a ranked roadmap of what to fix, improve, rebuild, or leave alone.
What I look at
- UX friction
- Performance
- Accessibility
- Frontend bloat
- Forms and conversion paths
- Tracking clarity
- Search and structure
- Fix vs rebuild decisions
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.
Frontend health snapshot
Speed
48CLS
Needs workA11y
72UX clarity
58Sample 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.
Frontend work that ships
Not just recommendations. Real fixes, features, and product work that ships.
Once the next step is clear, I implement it: cleanup, polish, components, tracking, workflows, and focused features for the sites and apps you already have.
Friction Found04
Hero images are oversized.
Performance drag on key pages.
Quote form errors are unclear.
Users abandon before submitting.
Mobile nav loses focus.
Keyboard path is unreliable.
Fix In Progress03
Standardize product cards.
Shared component and content rules.
Implement booking CTA tracking.
Know which pages drive action.
Clean unused scripts.
Reduce weight before rebuilding.
Shipped Improvement03
Accessible form states.
Labels, errors, focus, and validation.
Service page template cleanup.
Clearer path to inquiry.
Incident report export flow.
Focused internal tool workflow.
Founder note
Josh Hanson
Founder, Emery Studio
I'm the one diagnosing the problem and doing the work.
I started Emery Studio for businesses that need senior frontend help without the ceremony of a big agency. I've worked across creative agencies, ecommerce platforms, SaaS products, internal tools, component systems, tracking, accessibility, and frontend performance.
You don't get passed between sales, strategy, design, and development. You work directly with the person looking at your product decisions, frontend implementation, and customer experience together.
Start a conversation- No account managers, handoffs, or translation layer.
- Recommendations shaped by how the work actually gets built.
- UX, frontend engineering, accessibility, performance, and maintainability handled together.
- Clear priorities before you spend a dollar on a rebuild.
10 yearsAcross frontend, UX, ecommerce, product, and agency work.
200+ storesFrontend work for a national retail platform.
DirectYou work with the person doing the work.
After the audit
How the roadmap turns into shipped work.
The audit gives you the plan. From there, pick the level of help that fits, or take the roadmap and run it yourself.
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.
Contact
Tell me what feels slow, messy, unclear, or broken.
Send the site or app, what's frustrating you, and whether you think you need diagnosis, improvement, or build work. I'll point you to the right first step.
Prefer email? Reach me at hello@workwithemery.com