Skip to content
Swift Pages

Case study

How we moved swifteq.com off WordPress

swifteq.com ran on WordPress with the Divi page builder: 352 addresses, 42 hand-built pages and 192 blog posts. In October 2026 we moved it to Swift Pages, in a new design. Here's what it took and what changed.

Faster on every measure

speed score, desktop (Google PageSpeed)
53 → 100
speed score, desktop (Google PageSpeed)
until the main content shows, desktop
1.8 → 0.5 s
until the main content shows, desktop
accessibility score
81 → 100
accessibility score
home page size, in KB
625 → 53
home page size, in KB

Google PageSpeed, desktop: old site on 30 September, new site on 3 November 2026.

Five steps, each one checked

  1. 1

    Capture

    Every page, post, image and search tag of the old site recorded: 352 addresses and 4,157 uploaded files.

  2. 2

    Rebuild

    Pages turned into the new site's sections and posts into plain text files, in a new design.

  3. 3

    Check

    Every old address compared with its new page: words, prices, headings, images and search tags. 87 old addresses and 9 patterns now redirect.

  4. 4

    Review

    We went through the new site page by page with Claude: about 60 changes in two hours, none of them on the 192 blog posts.

  5. 5

    Launch

    A dry run on test names, then a one-hour switch on 12 October.

About five and a half hours of the owner's time

  • 1.5 hours during the move

    Decisions and account steps.

  • 2 hours of review

    Page by page, about 3 minutes per hand-built page.

  • 2 hours for the launch

    Much of it learning one DNS host's quirks.

Changes in minutes, not afternoons

The first edit through the Swift Pages connector, a highlight in the home page heading, took 1 minute 10 seconds from asking Claude to a preview, and 51 seconds from "publish" to live.

Bigger changes are just as quick. When we redesigned our MCP Server page, writing the copy was the slow part: once it was done, Claude rebuilt the page in a few minutes. On the old WordPress site, a redesign like that meant an hour or more in the page builder, and even a new heading took ten minutes of clicking.

If you put effort or budget into a migration, also make it better. Don't copy it pixel by pixel.

Sorin AlupoaieFounder, Swifteq

Want the same for your site?

Send us its address and we reply within one working day.

Page last updated