Taking a strong, high-traffic platform even further.
A high-traffic commercial site off WordPress and onto static-at-the-edge: 4,439 pages, 29 languages.
Ongoing engagement
Win: Real-user LCP passing at p75 (2,388ms) across 4,439 pages in 29 languages.
The results
WordPress → Astro
4,439 pages migrated
Custom CMS
16-language pipeline
8-year low
Bounce rate, first deploy
What was in the way
An established, high-traffic platform in the VPN and premium domain space, with real authority and reach — and a WordPress stack underneath it. The risk in a rebuild is not the design, it is the inventory: 4,439 content files across 29 languages, every one of them a URL somebody already ranks for. Lose a fraction of that and you have not rebuilt the site, you have caused an outage with better typography.
What it is
A conversion-focused platform rebuilt as a static site served from the edge, carrying its full content inventory and all 16 translated languages across intact. A partnership to take an already-successful site further in how it is built, managed, localized and served.
What I built
Every page brought under one design system and a modern build pipeline, then the whole inventory migrated: 1,050 pages and 3,389 posts, with 113 English source posts fanning out into 29 languages. Content edits that took hours take minutes, and new pages ship the same day. It runs on its own Cloudflare account, separate from everything else I run, with a dedicated content-editor Worker so the team edits without touching the repo. The project carries its own written agent contract, so a cold worker — human or AI — cannot break it by guessing.
Before and after
Before
After
Provider review page, refreshed for clarity and conversion
Before
After
Domain broker, sharpened positioning and focused CTAs
The outcome
Bounce rate dropped to an 8-year company low on the first deploy. Performance is measured continuously rather than claimed: over a recent 7-day window, real-user LCP came in at 2,388ms at p75 — inside Google's 2,500ms good threshold — across 2,406 samples, with crawler-measured server response averaging 258ms over 2,019 checks.