Frontend & UX
Modern frontend and UX that converts
Magento's legacy frontend (Luma, Blank) is obsolete: heavy, slow and with mediocre UX. We build frontends with Hyvä Themes — 10x faster than Luma, no Knockout.js, with Alpine.js and Tailwind. Or if you prefer, 100% custom design from scratch.
Hyvä Themes — the modern frontend for Adobe Commerce
Hyvä replaces Luma with a modern stack: Tailwind CSS + Alpine.js + no jQuery, no Knockout.js, no RequireJS. The result: ~50kb of JS instead of ~1MB. Perfect Core Web Vitals. 10x better developer experience.
We're official Hyvä licensees and have shipped dozens of stores on this stack across Mexico and LATAM.
- JS <100kb total (vs 1MB+ on Luma)
- Tailwind CSS for styling
- Alpine.js for interactivity
- LCP < 1.5s on product pages
- Lighthouse score 95+
- 2x faster dev velocity
UX/UI that converts
A pretty design without conversion data is art, not design. Our UX process includes research with real users, wireframes, navigable prototypes, moderated usability tests and post-launch heatmaps.
- User research with interviews
- Wireframes + Figma prototypes
- Usability tests with 5-8 users
- Post-launch heatmaps (Hotjar)
- A/B testing of variants
- Data-driven iterations
Obsessive performance (Core Web Vitals)
Google penalizes slow stores in ranking. Users abandon if LCP > 3s. Our builds target LCP < 2s, CLS < 0.1, INP < 200ms. Continuous monitoring with Real User Monitoring.
- LCP < 2s (target 1.5s)
- CLS < 0.1 (no layout shift)
- INP < 200ms (interactivity)
- Lazy-loaded images + WebP/AVIF
- Inlined critical CSS
- RUM with web-vitals.js
Alternatives: custom frontend or PWA Studio
Beyond Hyvä, we build 100% custom frontends (React, Next.js, Vue) if the project justifies it. For very specific cases we use Adobe PWA Studio (headless Magento with GraphQL). We help you pick the right one.
- Next.js + Magento GraphQL (headless)
- Vue Storefront (headless)
- Adobe PWA Studio (official)
- Nuxt.js for SEO-first
- Custom React with SSR
Accessibility (WCAG 2.1 AA)
Accessibility isn't optional — it's a legal requirement in several countries and it's the right thing to do. All our frontends meet WCAG 2.1 level AA: contrast, keyboard navigation, screen readers, aria-labels.
- AA contrast on all text
- Full keyboard navigation
- Screen reader compatible (VoiceOver, NVDA)
- aria-labels on interactive components
- Visible focus and logical order
- axe-core audit in CI
Frequently asked questions
Does Hyvä work with my existing Luma modules?
How much does a Hyvä license cost?
Can I have a headless checkout but keep the catalog on Luma?
Related services
Composable Commerce
Composable / MACH architecture on Adobe Commerce: API-first, headless, best-of-breed. Implementation with PWA Studio, decoupled frontend and microservices.
Learn more →Adobe Commerce PWA Studio
PWA Studio — Adobe's official framework for Adobe Commerce headless frontend with React + GraphQL. App-like storefronts with superior performance.
Learn more →Adobe Commerce
Adobe Commerce (formerly Magento) implementation with all native capabilities: catalog, checkout, payments, promotions, Page Builder and more.
Learn more →Conversion Rate Optimization (CRO)
eCommerce conversion rate optimization: research, hypothesis-driven testing, personalization, checkout UX, cart abandonment reduction. Proven methodology.
Learn more →Want to discuss your project?
We'll assess your case at no cost and propose a concrete path forward.
Book a call