Evaboot, February 2026 to April 2026
Situation: every content change went through a developer, hosting costs were high and the site performed poorly
The marketing site ran on WordPress. Every content change needed a developer. The site also performed poorly on Core Web Vitals (Google's speed metrics). And all of this at a high cost.
Mission: migrate the site and its blog, without losing content or URLs.
I recommended the new stack: Astro for the site and Sanity to edit the content. Then the site had to move over, keeping the content and the URLs, so the team could edit it on its own.
Actions
An audit first. I audited the WordPress site and chose the stack.
The content model. I exported the content and built its structure in Sanity in one day.
Pages and redirects. I migrated the pages and the blog, and checked the URL structure and the redirects.
Nine languages. I rebuilt the navigation, the author pages and the translations in all nine languages.
A faster site. After launch, a third-party script slowed the pages (an INP of 247 ms and 94 ms of blocking time). I deferred its loading and both problems went away.
A cut-over in three phases. First the DNS moved to Cloudflare, with no change for visitors. Then the domain switched to the new site. Finally the checks: redirects, sitemap submitted to Google, errors tracked for six weeks.
Results
Core migration done in about two weeks.
Nine languages live.
The team edits content in Sanity, without a developer.
Lighthouse in March 2026: 100 for performance, 93 for accessibility, 100 for best practices, 100 for SEO.
0 likes · 5 views · Oct 20, 2026
A B2B SaaS marketing site moves from WordPress to Astro and Sanity in two weeks, with no downtime. The team now edits content without a developer.
Timeline
Feb 1, 2026 - Apr 30, 2026
