Website Speed Optimization and Migration to Astro.js
A slow site costs you visitors: while it loads, the person goes back to the search results. I measure what exactly is slowing your site down and tell you what is worth fixing in place and what is worth moving. Based in Kaunas, Lithuania, working with clients anywhere.
Updated
What this gives you
Three reasons to speed a site up instead of rebuilding it from scratch.
Speed you can put a number on
Before and after — the same PageSpeed Insights test on the same pages. Not a feeling that it got faster, but numbers you can re-check yourself at any time.
Content and URLs stay where they are
Page addresses do not change, and where something has to change, a redirect stays behind. Meta tags, structure and text move across as they are: a migration should not look like a brand new site to Google.
You still edit it yourself
The content stays in a comfortable CMS — Sanity, or the same WordPress in headless mode. A developer is needed for new features, not for changing a sentence or a photo.
When to optimize and when to migrate
A slow site is almost never slow for a single reason. Usually several things stack up at once: unoptimized images, ten plugins of which three are actually used, a theme that loads its own fonts and styles on every page, and hosting that responds slower than it should.
The good news is that the first three are fixable in place — no migration, and cheaper. Migrating pays off when the problem is not in the content but in the foundation: when the site rests on a pile of plugins, when the theme generates half of the unnecessary code, or when every update carries the risk that something stops working.
That is exactly what the audit is for — so the decision rests on numbers rather than on a hunch.
What usually slows a WordPress site down
- Images at original size. A camera photo weighs several megabytes; the page needs a few hundred kilobytes of it.
- Fonts from external servers. Every extra font is another connection before the text appears on screen at all.
- Plugins whose code loads everywhere. A contact form plugin often loads on pages that have no form on them.
- A theme that does too much. Universal themes ship features for every possible case at once, and you pay for the ones you do not use in speed.
- Hosting. The cheapest shared plans respond slowly even when the site itself is in order.
What migrating to Astro.js means
Astro.js generates pages in advance — the visitor gets ready-made HTML instead of a result the server assembles on every request. JavaScript is shipped only where it is genuinely needed.
The content stays in a CMS: usually Sanity, but the same WordPress in headless mode works too — the admin panel stays exactly as it was, and only what the visitor receives changes. The site becomes fast without taking away your ability to edit it.
You can check how that works out on this site: it is built on the same principle, and you can run the test yourself with PageSpeed Insights.
What you have at the end
A fast site with the same content and the same addresses, a comfortable way to edit it, and a short walkthrough on how. If you need help later, hourly maintenance starts at €8/hr — bug fixes, content updates, new features.
How the work goes
Audit
I measure the site under real conditions — speed on mobile and desktop, image weight, fonts, plugins, server response. The result is a list of what is actually slowing it down, ordered by impact.
The decision: optimize or migrate
Often it is enough to fix what is already there, and that is cheaper. When a site rests on dozens of plugins, or a theme that generates half of the problem itself, migrating pays off sooner. I say plainly which option is cheaper in your case, even when it is the smaller job for me.
The work
For optimization — images, fonts, unused code, caching. For migration — Astro.js with a headless CMS, with all content and the URL structure carried over one to one.
Switchover
The new site goes live in parallel, so there is no downtime when we switch. After the switch I check the forms, the links and indexing in Google Search Console.
FAQ
Questions that come up before we start.
Will I lose my Google rankings?
Not if the migration is done properly. I audit what already works — the content, the rankings, the URL structure — and rebuild the rest. Addresses stay the same or get redirects, meta tags and schema.org markup move across with them, and the site is submitted to Google Search Console right away.
What does it cost?
Quoted individually — it depends on the scope and the state of the current site. The audit shows the exact scope before the work starts, so there are no surprises later. Smaller speed work fits the hourly rate from €8/hr.
Do I have to leave WordPress?
No. Often it is enough to speed up what you already have. If you want to keep the familiar interface, I also work with WordPress directly, including Divi 5, or run that same WordPress in headless mode: the admin panel stays as it is while the visitor-facing part becomes fast.
How long does it take?
It depends on the number of pages and the integrations. I give the exact timeline after the audit, once the scope is visible — guessing before that would not be honest.
Where will the site be hosted?
Your choice — Hostinger, Vercel or Cloudflare. If hosting is already in place, I continue with it instead of moving anything.
What is next
Let us start with an audit
Send me the address of the site — I will look at what is slowing it down and tell you whether to speed it up in place or move it.
Get in touch