← All Posts
November 5, 2026
Webflow Development
6

Moving My Own Site Off Webflow, Checked Page by Page

I moved gregoiregeoffroy.com from Webflow to a static build on Cloudflare. The move was boring on purpose: every page was diffed against production before cutover, and almost every number improved.

I build Webflow sites for a living, and until November 4 my own site ran on Webflow too. It doesn't any more. It is now a static build served by a Cloudflare Worker, and this post covers why, how the move was checked, and what changed in the numbers.

Why My Site, Specifically

Most of the work on this site already ran through the Webflow API and a git mirror, not the Designer. At that point the Webflow layer was mostly cost: pasting head and footer code and byte-diffing it to be sure it landed, working around the 10k character embed and 50k custom-code limits, API calls that silently did nothing (SEO fields, classes and attributes dropped on insert), all-or-nothing publishes, and jQuery plus webflow.js loaded with no way to remove them.

Two smaller reasons: a French version is cheap on a code site (no Localize add-on, no word cap, no English fallback served at /fr), and the $29 a month site plan goes away.

In my view, none of that applies to a site where a marketing team edits pages in the Designer every week. It applies to a site that is maintained like code.

The Rule: Prove Nothing Changed Before Anything Changes

The site had 25 URLs in its sitemap: 8 static pages, 15 case studies, one tip and one blog post, about 19,000 visible words. The goal for the first release was zero visible difference, so every check compared the new build against live production:

  • Rendered pages. All 25 URLs plus the 404, at 1440 px and 390 px: element geometry, computed styles, visible text, titles and status codes.
  • The head. Title, description, canonical, robots, language and social tags: 26 of 26 pages identical.
  • Content. 273 of 273 CMS fields matched after the export.
  • Machine-readable files. llms.txt and robots.txt byte-identical, and the JSON-LD graph has the same nodes on every URL. On the case study, tip and post templates it is now in the HTML itself instead of being assembled in the browser by a script.

The comparison also caught something on the live Webflow site: a default text block sitting under the home page footer, reading "This is some text inside of a div block." It was not ported.

What the Numbers Did

Lighthouse, medians of three runs on the same local harness (simulated throttling), Webflow production against the new build before cutover:

Measure Webflow Static build
Mobile performance: home, /work, case study 100, 90, 98 100, 99, 100
LCP on /work 3,364 ms 2,146 ms
LCP on a case study 2,013 ms 952 ms
Desktop CLS 0.031 to 0.095 0
Page weight 503 to 723 KB 217 to 296 KB

One measure got worse: desktop LCP on the home page went from 299 to 333 ms, inside run-to-run noise. After cutover, PageSpeed Insights on mobile gave the production home page 100 in all four categories on three runs out of three, with an LCP of 0.9 to 1.3 seconds and no layout shift.

The Cutover

DNS had already moved to Cloudflare. On November 4 at about 16:21 UTC the Webflow records were deleted and both hostnames were attached to the Worker; www was serving the new build with a valid certificate about a minute later (a few resolvers kept the old records for some minutes more).

Then Search Console. The domain property verification survived the nameserver change, the sitemap was resubmitted (25 URLs, no errors), and the home page plus two case studies inspected as "Submitted and indexed". Google's last crawls of those pages still predated the cutover, so the real confirmation is the next crawl.

Things That Got Simpler

Analytics. GA4 had only been counting visitors who clicked Accept on the cookie banner; everyone else sent cookieless pings that never show in reports. The site now uses Cloudflare Web Analytics, which sets no cookies, so the banner, Google Tag Manager and GA4 are removed from the site.

Forms. The free audit form posts to the Worker, which stores each request in a database before sending the notification email. If the email fails, the lead is still there.

Content. Each case study, tip and post is a Markdown file in the repository. An edit is a commit, and recovering any earlier version of the site means redeploying an earlier commit.

Every deploy is checked. Before anything is uploaded, a script checks every built page for a title and description, a canonical that matches the URL, exactly one H1, JSON-LD that parses, image dimensions and alt text, and working internal links. One failure stops the deploy.

French the Next Day

The day after cutover the site went bilingual: every page except the legal one now exists in French, with hreflang pairs and a language link in the navigation. Because the claims on these pages have to stay true in both languages, a script checks that every number in an English case study, tip or post appears in its French version.

One Lesson From the Numbers

A fast build can still have a slow page. On /work, the largest image arrived early but waited about two seconds for its scroll-reveal animation before it was allowed to paint, and Lighthouse counted all of it. The first card now skips the animation. If a page's LCP looks wrong, read the breakdown before blaming the network: the delay can be a script that hides the element on purpose.

Would I Do This for a Client?

I would only recommend it when the site behaves like code: maintained through an API or a repository, heavy on custom scripts, and not edited in the Designer every week. For most marketing sites, I think Webflow's editor is the point.

Post
Long Form
Topic
Webflow Development
Published
November 5, 2026
Read
6
Written by
Gregoire Geoffroy
Contents
In This Post

See What Your Site Is Missing

Start with a free audit of your site, checked by me. Or book thirty minutes with your project on screen: you leave with a scoped plan and a number, whether or not we work together.

Grégoire Geoffroy
Grégoire Geoffroy
Webflow Partner
Free audit
Report link within 3 business days
Call
30 min · Google Meet
Time zone
Europe/Paris
Reply
Within one business day