HappyLipo: from Webflow to Astro and Sanity.
We built happylipo.de, first in Webflow. Since September 2026 the platform runs on Astro with Sanity as its editing system and Cloudflare in production.
Astro 7 in production
Static HTML from the build, delivered through Cloudflare.
Editing without an agency
Articles, topic pages and downloads are written in Sanity Studio.
Measured on 10 Sep 2026
Lighthouse 99 on desktop, 94 on mobile, 0 ms blocking time.
A content platform on lipedema.
Screenshots from production, captured on 10 September 2026.
Client project · website
HappyLipo
Content platform on lipedema: knowledge articles, nutrition, care and downloads. Built by us, first in Webflow. On Astro with Sanity as the editing system since September 2026, maintained by the client.
How the website is built today.
-
Content lives in Sanity
Every article, topic page and download is a record with fixed fields. The website reads them at build time.
More on this
A post carries a title, category, author, image, summary and body text. The summary appears above the article and in the
abstractfield of the article schema, so search engines and AI answers read the same short version. When a headless CMS is the right call is covered on our headless CMS agency page. -
Images are made at build time
Astro derives several WebP sizes from each source image. The browser downloads the one variant it displays.
More on this
The home page carries 18 images and weighs around 500 kilobytes together, measured in the Lighthouse run on 10 September 2026. Because the dimensions sit in the markup, layout shift stayed at 0.018 on desktop and 0 on mobile.
-
Every page type has a schema
Articles emit BlogPosting with author, date and summary, plus a breadcrumb up to the topic page.
More on this
The schema is built from the same fields as the visible page, so the two cannot drift apart. An SEO audit then checks whether Google reads the markup the way it was meant.
-
What we handle differently
On import, every migrated post carried the same publication date. The created date from the export belongs in that field.
More on this
Webflow keeps a created date per item. During the move into Sanity the import timestamp landed in the date field, visible under each post and in the article schema. In new projects we carry the created date across as its own field and check it before the switch. The process is described under Webflow to Astro migration.
Thinking about your own site?
Send us the address of your Webflow site and the reason behind the question. You get an assessment of whether a move pays off for you.
The Lighthouse run on the home page.
Desktop measurement from 10 September 2026, Lighthouse 12.8.2, verifiable at any time.
Questions about this project.
Why Sanity and not Markdown in the repository?
The editorial side works without developers and needs forms, media management and drafts. Content in the repository would have meant a pull request per article. Which system fits which team is covered under Astro CMS.
What does the mobile measurement show?
The mobile Lighthouse run on 10 September 2026 returned Performance 94, Accessibility 94, Best Practices 100 and SEO 100. The largest content painted after 2.5 seconds and blocking time was 0 milliseconds.
Who maintains the content today?
The client herself, in Sanity Studio. Recurring edits to the same content can also run through chat, which we describe under edit your website by chat.
How did search visibility develop?
We do not publish figures from the client's Search Console. What we can show is the delivery measurement and the structure behind it. For your own project we measure before and after the switch.
How long does a move like this take?
It depends on the content volume and how much of the interface is rebuilt. Typical timeframes are listed under migration to Astro, the cost logic under Astro development cost.
Do you still build in Webflow?
Yes, this website started there. For teams that build pages themselves every day, the visual editor stays the better tool. The trade-off is covered under Astro vs. Webflow.
More from the Astro cluster.
The topics behind this project.
Is a move coming up for you?
Tell us briefly what is getting in the way today. You get an assessment, not a pitch deck.
Talk about your project.
Website address, the reason, your timeframe. We sort out the rest on the call.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related services.
Webflow to Astro migration
When the move pays off, when you are better off staying and what carries over.
Learn moreWebflow Agency
We still build in Webflow when your team publishes pages every day.
Learn moreSupport and maintenance
What happens after the switch: updates, measurement and operations.
Learn more