Venari Partners' old website ran on Wix and held 290 articles. We rebuilt it as a headless website: the code runs on Astro, the content sits in Storyblok and the site is hosted on Cloudflare. It launched on 1 October 2026. Tested with Google PageSpeed Insights on 22 October 2026, it scored 95 for performance on mobile and 97 on desktop. This piece covers the build. The main Venari case study covers the whole project.
A headless website keeps the content in one system and the code that displays it in another. The marketing team edits text, people and articles in a content editor. The design, page structure and performance are controlled in code, which the editor can't change by accident.
In our view, builders like Wix trade control for convenience. Content and layout share one place, so editors work on the layout itself and small edits can shift it. That suits teams who want to change layouts themselves.
Venari had a new brand and a marketing team that regularly adds consultants, articles and practice pages. We wanted those edits to be easy without letting the site drift away from the brand. We also wanted the site to load quickly.
Because of who edits the site. Page builders add code to support visual editing, so the team can change layouts as well as content. Venari's team changes content often but doesn't need to change layouts, so we left that weight out. In our view, less code makes a page quicker to load and simpler for search engines and AI tools to read.
It is a trade-off, not a rule. For a hotel team that wanted design control, like the one at Priory Wareham, a page builder was the right call.
Venari's brand is built on Pace, Detail and Care. Pace shows in the speed scores below. Care shows in the structure: from the homepage to the menu, Venari's consultants come first. The practices and services follow from them. That order came straight out of the brand strategy.
The homepage and the core of the site are written in code. The sections that change over time are connected to Storyblok: consultant profiles, articles, practice and service pages, testimonials and calls to action.
The content is linked rather than copied. Each article has an author. Each consultant's profile lists the articles they have written. Each person can be assigned a sector. The site then places them on the right pages. A new profile or article starts as a copy of an existing one, so the team fills in fields rather than building layouts.
Homepage changes still come to us. That is deliberate. The homepage carries the brand and most of the first impressions, so it stays in code.
Wix had no way to export the articles in a form Storyblok could import. Copying 290 articles by hand would have taken weeks. We used AI to extract the content from the old site and format it for import instead. We then checked the imported articles and corrected any formatting errors by hand.
The homepage and core pages are hard-coded for speed. The site is hosted on Cloudflare.
These are the live site's PageSpeed Insights scores on 22 October 2026:
The cookie banner costs a couple of performance points. These are lab scores from a test run on one day, not measurements of real visitors. Google explains the difference in its guide to PageSpeed Insights.
We handed the site over on a call with Venari's marketing team on 30 October 2026 and followed it with a recorded video tutorial. The working rules are short. Save as often as you like, then publish in one batch. Publishing takes a minute or two, because the content and the code are hosted separately. Add alt text when you upload an image.
If your site barely changes, or one person updates it twice a year, a headless build is probably more than you need. It pays off when a team edits the site often and you also care about how fast it loads and how consistently it carries the brand.
You can read more about how we build on the Modernise Infrastructure page, or email studio@mouriaux.com.
Written by Tom Le Mesurier, Principal, Mouriaux.
