Moving Akveo.com From Webflow to Astro With Claude Code

We moved our website off Webflow onto our own code with Claude Code. Now marketing edits the site with an AI agent, and the homepage ships 9 KB of JavaScript instead of 340 KB.

[ Client ]

About the Client

Akveo's own website: more than 250 pages, built on Webflow. The goal was to move the site to our own code so marketing could make changes with an AI agent.

340 KB → 9 KB
JavaScript on the homepage: 3–4 s → 0.1 s
to open a page in development: 1 day
for each of our next two sites

[ Challenge ]

Webflow Kept the Developer in the Loop

Webflow was the right choice for a while. We moved to it to take the developer out of the chain: marketing → design → developer → website.

The Developer Didn't Really Leave

You still needed a designer who knows Webflow.
The platform hit its limits, and the site filled up with workarounds.
Every change took a long time.

Heavy Pages

The homepage loaded 30 JavaScript files, 340 KB, including two different versions of jQuery.

[ Solution ]

Building the Solution

We exported everything from Webflow: 19 CMS collections as CSV, and the site as HTML and CSS. Then we moved it to code with Claude Code.

First Attempt: Next.js

All 280 URLs opened and looked like the original. Inside, the agent took “exactly like the site” literally: the same testimonial sat in 99 files, the contact form in 258, and content was stored in TypeScript.

Content in Markdown

When we needed German, content in TypeScript meant copying everything again. We rewrote all content in Markdown. The AI trends article went from 767 lines of TypeScript to 218 lines of Markdown.

Switching to Astro

In Next.js every page pulled in the whole site: 706 imports, 353 documents. Opening one page took 3–4 s and up to 2.5 GB of memory. Astro fixed it: 0.1 s and 0.95 GB for the whole site.