Rocksoft, the software house behind Diligently, moved its own three-language website off Webflow onto Astro and Bee CMS. Mobile PageSpeed went from 46 to 91, and changes that used to take weeks now take an afternoon.
Key takeaways
- Two reasons drove the move: a slow site (mobile PageSpeed 46, LCP 9 seconds) and a change process that went through copywriting, design and development and took weeks.
- The hard part was dozens of landing pages with their own one-off designs. We mapped them onto a small, fixed set of CMS blocks with layout variants instead of adding new block types, so the site stays easy to maintain.
- Mobile Performance went from 46 to 91 and Desktop from 60 to 98, with Accessibility and SEO both at 100. A mega menu we had discussed for a year was built in an hour.
Rocksoft is the software house Diligently belongs to. Its website sells web and mobile app development, product design, AI engineering and a handful of fixed-price starter services, in English, German and Norwegian. Until September 2026 it ran on Webflow. Today it runs on Astro with Bee CMS, the same platform we move our clients to.
This is the case study we are most critical about, because it is our own site. Here is what pushed us, what was harder than expected, and what changed.
Why we left Webflow
There were two reasons, and neither was the price.
1. Performance. In December 2024 we opened an internal ticket titled “Rocksoft website loading speed”. Fonts were showing up seconds late, and PageSpeed measured 13 seconds to First Contentful Paint on mobile. We tried to fix it inside Webflow for months. The last measurement before the move, on 15 September 2026, still showed a mobile Performance score of 46, with First Contentful Paint at 8.8 seconds and Largest Contentful Paint at 9 seconds. For a company that sells software engineering, that was an awkward first impression.
2. The speed of change. Every update to the site went through the same relay: someone wrote the copy, a designer turned it into a layout, a developer built it in Webflow. Each handover meant waiting. A new landing page or a reworked section regularly took weeks, and small ideas simply never made it out of the backlog.
The hard part: dozens of pages with their own design
Rocksoft.pl was not a template site. Over the years almost every service and campaign got its own landing page with its own design: the Discovery Workshop, the Code Audit, the UX Audit, the AI engineering offer, the partnership programme, the case studies. Recreating each page pixel by pixel would have been the quick route, and the wrong one. A site where every page is a custom build is exactly the site that is hard to maintain, and hard for a copywriter, or an AI assistant, to change safely.
So we set one rule: no new block types. Every page had to be composed from the same standard CMS blocks the rest of the platform uses: hero, features, pricing table, FAQ, comparison table, call to action, and so on. Where a page genuinely needed a different look, we added a layout variant of an existing block in code. The content stays in the CMS, editable and translatable. Only the look lives in the code.
The rule was tested early. One of the first commits moved some copy straight into a component, because that made the page match the old design faster. Code review caught it, and the copy went back into the CMS. That review comment is the whole philosophy in one line: if the text sits in the code, the person who writes it can no longer change it.
The rest of the move was ordinary migration work across three languages: contact forms on the translated pages, the language switcher, missing translations (we added a CMS tool that lists them, so they no longer fall back to English unnoticed), image optimisation, and a sitemap we had forgotten to switch on at launch. From the first commit to switching the DNS took about two weeks.
The result
Google PageSpeed Insights, same homepage, on Webflow (15 September 2026) and on Astro + Bee CMS (27 October 2026):
| Webflow (before) | Astro + Bee CMS (after) | |
| Mobile Performance | 46 | 91 |
| Desktop Performance | 60 | 98 |
| Mobile First Contentful Paint | 8.8s | 1.7s |
| Mobile Largest Contentful Paint | 9.0s | 3.2s |
| Desktop Largest Contentful Paint | 4.9s | 1.1s |
| Mobile Cumulative Layout Shift | 0.214 | 0 |
| Desktop Total Blocking Time | 280ms | 0ms |
| Accessibility / SEO | 93 / 92 | 100 / 100 |
The mobile numbers are the ones that matter. A visitor on a phone used to look at an empty screen for almost nine seconds. Now the page appears in under two, and nothing jumps around while it loads.
Webflow — Mobile · 46 | Astro + Bee CMS — Mobile · 91 |
Webflow — Desktop · 60 | Astro + Bee CMS — Desktop · 98 |
The bigger win: changes in hours, not weeks
Speed scores are easy to show. The change we feel every day is in how we work.
The copy-design-development relay is gone. The person who writes the copy now works straight in the CMS and sees the finished design in the page preview while typing. There is no mock-up to wait for and no handover to a developer for a new section, because the blocks already carry the design. When something does need code, like a new layout variant, it is a small, contained change that an engineer, often with an AI assistant, ships the same day.
Our favourite example is a recent one. We had wanted to rebuild Rocksoft's menu and navigation since last year. It came up in meeting after meeting and never got done. One morning in October it came up again. An hour later we had a full mega menu: every service line with its own colour, the fixed-price starter services with their prices, and a featured card for our AI engineering offer.
The new rocksoft.pl mega menu: a year of discussions, one hour of work.
For years our own website was the one project nobody had time for. Every change meant a copy doc, a design round and a slot in the development queue, so good ideas quietly died in the backlog. Now whoever writes the copy sees the finished page in the preview before anyone else touches it. The mega menu says it all: we talked about it for a year, and it took an hour. We're very happy with the move. My only regret is that we didn't do it sooner.
Edwin Nooitgedagt
Head of Delivery, Rocksoft
Running a Webflow site that has grown into dozens of one-off pages? See the four fixed ways to move off Webflow, from a $490 static export to a full Astro + CMS rebuild, or read how we did it for Kwalitet.