How I Moved My Own Site Off WordPress: Before and After
Until 15 November 2026, the site you’re reading ran on WordPress with the Elementor page builder. That day I moved it to a static site built with Astro. I offer this migration to clients, so I did it on my own site first. This post covers what I did step by step, what changed in the measurements, and what I gave up.
All numbers come from Google’s PageSpeed Insights, on the mobile setting, for the home page. A single run can mislead, so I measured three times before the move and three times after.
Why I Moved
The site worked, but three things bothered me:
- It was slow on phones. The mobile performance score bounced between 79 and 85. In some runs the main content took 3.8 seconds to appear; Google’s recommended limit is 2.5 seconds.
- The page was heavier than it needed to be. The home page HTML alone was 222 KB, with 93 links to separate theme and plugin files. Visitors’ phones were downloading a lot of code for things they never saw.
- Maintenance never ended. WordPress, the theme and the plugins kept asking for updates, and after each one I had to check whether something had broken.
What actually changed on the site was a few lines of text and a price now and then. That didn’t need an admin panel and a database running all day.
What Was Moved
I didn’t drop any content:
- Every page and all 6 blog posts came across with their full text.
- Images were moved, resized for the screen and re-saved as WebP.
- Each page’s title and description, the part people see in Google, carried over unchanged.
- The contact form was rebuilt on the new setup.
I also redesigned the site along the way, but the design wasn’t the real work of the migration.
The Real Work: Old URLs
The part most often missed in a migration is the old addresses. Every link sitting in Google, on other sites or in someone’s bookmarks points to an address on the old site. If that address doesn’t exist on the new one, the visitor gets a “page not found”.
Here’s what I did:
- Listed every old URL. Not just the pages in the menu: I also pulled old post slugs left in the WordPress database backup, removed pages, and the category URLs WordPress generates on its own.
- Matched each one to its new home. Pages whose address didn’t change kept it. For the rest I wrote a permanent (301) redirect. That came to 110 redirects.
- Tested them all on the live site. After the switch I opened each of the 110 redirects one by one and checked that it led to the right page and that the page actually loaded.
For example, the old /hizmetler/ (services) address now goes to the new services page, and the never-used /product-category/ addresses WordPress had created don’t end in a dead page either.
Switch Day
The new site was live at a separate preview address for days, while the old site stayed up. The actual switch is just pointing the domain at the new site.
The order was:
- Email first. My email address lived with the old hosting company, so it would have gone down with the hosting. I moved email to a separate service three days before the switch and tested that it worked.
- Pointed the domain at the new site. This took about ten minutes. One DNS record type didn’t work properly in the old provider’s panel; switching to a different record type fixed it. The SSL certificate was issued automatically within the same few minutes.
- Checked everything again. Redirects, the
wwwand non-wwwaddresses, the secure connection and the error page, one by one. - Tested the form with a real message. This is where a problem turned up: form detection was switched off on the new host, so the form looked like it was sending but nothing reached anyone. I turned it on and sent two test messages; both landed in the inbox.
That last step is why I test the form with a real submission on every migration. Nothing on the page showed an error.
After the switch I submitted the new sitemap to Google Search Console. If an old URL slipped through, it will show up there over the next few weeks.
Before and After
Same tool, same settings, same page. “Before” is the WordPress site on 13 November 2026, three runs. “After” is three runs on 15 and 16 November. Where the runs differed, I give the lowest and highest values.
| Metric | Before | After |
|---|---|---|
| Performance score | 79–85 | 98–100 |
| Main content visible (LCP) | 2.3–3.8 s | 1.2 s |
| First content visible (FCP) | 1.5–1.6 s | 0.8–0.9 s |
| Time the page was blocked (TBT) | 170–490 ms | 0 ms |
| Accessibility | 92 | 100 |
| Best practices | 96 | 100 |
| SEO | 100 | 100 |
| Home page HTML size | 222 KB | 37 KB |
The row I care about most is LCP: the time until a visitor sees the page’s main content dropped to 1.2 seconds in all three runs. The score moving between 98 and 100 is normal; PageSpeed simulates the network and device slightly differently each time. Here’s the report for the latest run.
One caveat: these are lab measurements, a test where Google simulates a mid-range phone on a slow mobile connection. Real visitors’ experience depends on their connection. But a before-and-after comparison under the same conditions shows the difference honestly.
What I Gave Up
The move has a cost, and it’s worth writing down:
- No admin panel. I can’t log in and edit text the way I could in WordPress; changes are made directly in the site’s files. On client sites I take this on: you send me the text you want changed and I publish it.
- No plugins. A feature you’d add with a WordPress plugin in two minutes has to be built by hand here. On my site, what the plugins did (contact form, sitemap, page titles) was already covered by the new setup.
For sites that change daily, have many people adding content, or have a cart and checkout, this trade may not be worth it. For a small business site that changes a few times a month, the gain is far bigger than the loss.
Thinking About Moving Your Site?
I use the same process for client sites: I go through your site page by page, build the new one at a separate address, match every old URL to its new home, and test each one on the live site after the switch. Prices are the same as for a new site.
Details are on the services page, and prices on the pricing page.