EMPOWR.studio

work / EMP—001 · internal case · built in public

This site, built in public.

Client
EMPOWR STUDIO (internal project)
Scope
Brand + bilingual ES/EN site + journal
Stack
Astro · edge · zero UI libraries · JS < 5 KB
Accessibility
WCAG 2.2 AA ✓
Status
Phase 05/07 · launch — updated live
fig. 01 — home, iteration 08 · prototype in Astrothe acid caret: the brand’s signature

No one hires you without cases, and there are no cases without clients.

A new studio without a portfolio faces that classic paradox. We decided to break it by turning our own launch into the first case — with the highest bar we’d set for any client: international-award calibre, AA accessibility and published metrics.

02 — Approach

Eight routes. One direction.

Before choosing a single colour we studied the studio market in Mexico and LATAM, twelve local competitors and their published prices, and the international references that set the bar. The direction came from eight divergent routes narrowed to one: Ácido Editorial — quiet luxury, surgically interrupted by a green that doesn’t ask permission.

  1. route 01
  2. route 02
  3. route 03
  4. route 04
  5. route 05 ✓Ácido Editorial
  6. route 06
  7. route 07
  8. route 08
  • Paper
    #FAFAF6 · backgrounds
    ink on paper 17.63:1
  • Ink
    #141412 · text · blocks
    paper on ink 17.63:1
  • Acid
    #C6F211 · the virus
    ink on acid 14.1:1
  • Stone grey
    #55554E · secondary
    on paper 7.2:1
AaAaINSTRUMENT SERIF
display · headlines
AaINTER
body text
AaSPACE MONO
data · sheets · terminal

03 — Our costliest lesson came from an iPhone

“Content exists first. Motion is a layer.”

The first versions of the prototype hid the content behind animations that depended on JavaScript — and the viewer used for reviews doesn’t run it. Result: a blank page.

The rule born from that mistake governs all the code: content exists complete and readable; motion switches on above it when the browser can. If you’re reading this, the rule works.

04 — Technical decisions

Technical decisions, in short.

  • a.Astro, static outputPlain HTML is unbeatable on speed.
  • b.Zero UI librariesNothing the browser downloads without need.
  • c.< 5 KB of our own JSAll of the site’s motion fits in it.
  • d.Bilingual /es /enFrom the architecture, not as a patch.
  • e.AA as a requirementBuilt in, not a last-minute audit.
  • f.Content firstWithout JavaScript, the whole site still reads.

05 — Result

Under construction — and that’s the point.

MetricExit gateProduction
Performance · Lighthouse≥ 95100 mobile · 100 desktop
SEO · Lighthouse≥ 95100 · 100
Accessibility · Lighthouse100100 · 100
Core Web VitalsgreenLCP 1.6 s · CLS 0.004 · TBT 0
Leads and projectsGA4 · 90 daysafter launch

Measured on 01.10.2026 in production (Spanish home) with PageSpeed Insights — Lighthouse 13.5, emulated mobile and desktop. Core Web Vitals field data arrives once there’s real traffic. Commercial results are reported with GA4 data 90 days after launch. No adjectives: numbers.

Next case — EMP—002 · in progressphase 02/07 Grupo González