Migrate from WordPress to Astro in Budapest
Many businesses in Budapest run WordPress but face performance ceilings, security overhead, and rising hosting costs. Astro solves these with static HTML output, zero JavaScript by default, and edge deployment. I migrate existing WordPress sites to Astro with full SEO preservation, URL mapping, and 301 redirects.
- PageSpeed 95-100
Static HTML with zero JavaScript. Faster than any WordPress solution.
- SEO-safe migration
URL mapping, 301 redirects, Google rankings preserved.
- Cloudflare Pages hosting
Global CDN, free SSL, instant deployments. Hosting costs near zero.
Budapest is one of Central Europe's primary hubs for financial technology, pharmaceutical and biotech research, automotive software engineering, and regional shared services. Across the modern corporate and R&D campuses along the Váci út corridor (District XIII), the deep-tech and university spin-outs at Infopark and BudaPart next to BME (Budapest University of Technology and Economics) in District XI, the technology centers along the Corvin Promenade (Corvin Sétány) in District VIII, and the financial headquarters in Belváros-Lipótváros (District V) and Graphisoft Park in Óbuda, engineering teams build digital platforms for Hungarian, DACH, and global markets. I engineer and migrate fast, maintainable web platforms using Astro, working as a solo software developer in Gdynia, Poland, collaborating with your Budapest team entirely in writing.
Why Budapest fintech, biotech, and SaaS teams build with Astro
Many Budapest companies outgrow their initial web stack when expanding into DACH and Western European markets. A legacy monolithic WordPress site slows down under heavy multilingual plugins and exposes /wp-admin and SQL endpoints to automated attacks, while a full React Single-Page Application (Next.js) forces every visitor’s browser to download and hydrate hundreds of kilobytes of JavaScript just to read static product pages or documentation.
Astro solves this architectural bottleneck by compiling your content into zero-JavaScript static HTML and scoped CSS at build time, while hydrating interactive UI components on demand via Astro Islands.
Multi-currency (HUF / EUR) islands and native i18n routing (hu, en, de)
For Budapest SaaS providers, B2B exporters, and e-commerce platforms operating across Hungary (hu in HUF with Hungary’s standard 27% ÁFA), DACH (de-DE / de-AT in EUR), and international English (en in EUR / USD), Astro provides a clean separation between static localized content and interactive pricing or checkout widgets:
---
// src/pages/hu/megoldasok/[slug].astro
import BaseLayout from '../../../layouts/BaseLayout.astro';
import FeatureComparisonTable from '../../../components/FeatureComparisonTable.astro';
import DualCurrencyPricingIsland from '../../../components/react/DualCurrencyPricingIsland.tsx';
import { getSolutionEntry } from '../../../lib/cms';
const { slug } = Astro.params;
const entry = await getSolutionEntry(slug, 'hu-HU');
---
<BaseLayout title={entry.seoTitle} description={entry.seoDescription} lang="hu">
<main class="solution-page">
<h1>{entry.title}</h1>
<p class="lead">{entry.summary}</p>
<!-- Static HTML: 0 KB client JavaScript -->
<FeatureComparisonTable rows={entry.features} />
<!-- Isolated React Island: hydrates only when scrolled into view -->
<DualCurrencyPricingIsland
client:visible
defaultCurrency="HUF"
vatRate={0.27}
tiers={entry.pricingTiers}
locale="hu-HU"
/>
</main>
</BaseLayout>Because the header, hero typography, specification tables, and legal footer ship as plain HTML, the browser paints the page immediately and leaves the main thread free. This architecture is engineered to meet Google’s official Core Web Vitals “Good” thresholds in real-user CrUX field data:
- Largest Contentful Paint (LCP): up to
2.5 s - Interaction to Next Paint (INP): up to
200 ms - Cumulative Layout Shift (CLS): up to
0.1
Hungarian statutory and regulatory compliance built into your Budapest Astro stack
A commercial website operated by a Hungarian Korlátolt felelősségű társaság (Kft.) or Zártkörűen működő részvénytársaság (Zrt.) registered in Budapest must comply with specific Hungarian statutory legislation published in Nemzeti Jogszabálytár (njt.hu) alongside European Union directives.
1. NAIH (Infotv. CXII/2011) and Eht. § 155(4) Cookie Consent Rules
In Hungary, personal data protection is governed by the GDPR and Act CXII of 2011 on the Right of Informational Self-Determination and on Freedom of Information (2011. évi CXII. törvény - Infotv.), enforced by the National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság - NAIH). Storing or accessing cookies and tracking identifiers on a user’s terminal device is regulated under § 155(4) of Act C of 2003 on Electronic Communications (2003. évi C. törvény az elektronikus hírközlésről - Eht.).
In my Astro builds for Budapest companies:
- Zero non-essential scripts before affirmative opt-in: Under § 155(4) Eht. and NAIH enforcement decisions, analytical and marketing scripts may not execute before the user provides explicit, informed opt-in consent. Because Astro outputs static HTML with zero third-party JavaScript by default, tracking tags remain completely inert until consent is recorded in your CMP.
- Self-hosted
.woff2web fonts: To prevent unconsented transfer of visitor IP addresses to US servers on initial load, I never load fonts fromfonts.googleapis.com. All web fonts (including full support for Hungarian double-acute characterső, űalongsideá, é, í, ó, ö, ú, ü) are subsetted and served directly from your first-party European origin.
2. Mandatory Hungarian Impresszum disclosures under Ekertv. § 4
Under § 4 of Act CVIII of 2001 on certain issues of electronic commerce services and information society services (2001. évi CVIII. törvény - Ekertv.), every commercial website in Hungary plays host to strict permanent disclosure obligations (Impresszum), actively audited by consumer protection authorities (Fogyasztóvédelmi hatóság) and the GVH (Gazdasági Versenyhivatal).
I wire a schema-validated global footer and /impresszum/ template that renders server-side across all language versions (hu, en, de):
- Full registered company name (Cégnév, e.g., … Kft. or … Zrt.).
- Registered seat (Székhely in Budapest, specifying the district I.-XXIII. kerület) and mailing address.
- Company registration number (Cégjegyzékszám:
01-09-XXXXXXfor a Kft. or01-10-XXXXXXfor a Zrt.) and the registering court (Fővárosi Törvényszék Cégbírósága). - Hungarian tax number (Adószám,
XXXXXXXX-2-4X) and EU VAT number (Közösségi adószám,HUXXXXXXXX). - Competent chamber of commerce membership (Budapesti Kereskedelmi és Iparkamara - BKIK under Act CXXXI of 1999).
- Direct electronic contact details (email and telephone) and full legal details of the web hosting provider (Tárhelyszolgáltató neve, székhelye, e-mail címe) - a specific statutory requirement under § 4(f) Ekertv. that is frequently overlooked on generic foreign templates.
- For B2C e-commerce platforms, mandatory conciliation board details (Budapesti Békéltető Testület,
bekeltet.hu) under Act CLV of 1997 on Consumer Protection (Fgytv.) and Government Decree 45/2014. (II. 26.) Korm. rendelet.
3. Hungarian Accessibility Act (2022. évi XVII. törvény) and Hybrid B2B / Payment Endpoints
Hungary transposed the European Accessibility Act through Act XVII of 2022 on the general rules for the accessibility of products and services (2022. évi XVII. törvény a termékek és a szolgáltatások akadálymentességi követelményeinek való megfelelés általános szabályairól), applicable from 28 June 2025.
When I engineer your Budapest Astro platform:
- Every page uses semantic HTML5 landmarks (
<header>,<nav>,<main>,<article>,<footer>), native<details>/<summary>accordions, and keyboard-accessible Astro Islands meeting WCAG 2.1 Level AA / EN 301 549. - Where server-side execution is required, such as validating Hungarian B2B tax numbers (Adószám) for NAV Online Számla invoicing (via Billingo or Számlázz.hu APIs) or handling OTP SimplePay, Barion, or Stripe payment webhooks, I isolate those routes as hybrid Astro server endpoints (
export const prerender = false) while keeping 95%+ of the site purely static.
How a project with me runs
I am Mariusz Szatkowski, an independent software developer based in Gdynia, Poland, operating in the exact same Central European Time zone (CET/CEST) as Budapest. When a Budapest company hires me, I write all TypeScript and Astro code myself without agency account managers or junior handoffs.
- Written-only engineering for Budapest teams: I work without phone calls, video calls, or live meetings. All Budapest technical specs, redirect maps, and code reviews are handled in writing via GitHub, GitLab, Jira, or email. Your Budapest developers and product leads get a precise, searchable written record they can review asynchronously.
- Design boundary on Budapest builds: Your Budapest designer or creative studio supplies the graphic design and Figma wireframes. Your in-house designer or Budapest creative agency supplies the Figma files (or I replicate your existing visual layout during a migration from WordPress, Webflow, or Next.js), and I implement them into clean, accessible Astro and Tailwind CSS code.
- What your Budapest team provides to start:
- Your live Budapest domain URL (for a migration) or a written functional specification (for a new build).
- Access to your Budapest Figma files or existing source repository.
- Your preferred CMS setup (Markdown/MDX, Sanity, Strapi, Directus, Storyblok, Contentful, or headless WordPress) and target locales (
hu,en,de). - Any required payment (SimplePay, Barion, Stripe), invoicing (Számlázz.hu, Billingo), or CRM integration specifications.
I reply in writing on working days and deploy every milestone to a private staging URL so you can verify Core Web Vitals, SEO metadata, and Hungarian statutory disclosures before production cutover.
Start your Astro project in Budapest
Integrating Hungarian NAV Online Számla, SimplePay, Barion, and DACH Portals
Budapest e-commerce and B2B platforms frequently combine domestic Hungarian checkout and invoicing stacks (OTP SimplePay, Barion, Számlázz.hu, Billingo, and real-time NAV Online Számla XML reporting) with international Stripe or Adyen flows for DACH and UK customers. In Astro, I isolate these server-side API integrations inside typed Astro Actions (src/actions/index.ts) and hybrid SSR endpoints so your public marketing and catalog routes remain 100% static and cacheable at the CDN edge.
If you want to launch a fast Astro website or migrate an existing Budapest platform away from a slow monolithic CMS or heavy SPA, send me your current URL, target languages, CMS setup, and timeline via my contact page. Your initial written Budapest scope review is free, and I reply in writing on working days.
Selected projects
Examples of my work.
Travel & Tourism Site: kaminski.pl
Kaminski.pl is a website created for traveler and blogger Michał Kamiński, who shared his experiences from exploring the world, inspiring others to discover ...
Vector Solutions - Telecommunications Technology Pioneer
Vector Solutions is a company recognized in Poland and throughout Europe as a pioneer in the technology sector, transforming modern communication with innovative solutions for cable operators and telecommunications companies.
Victim Assistance Office - odszkodowania.pl
The Victim Assistance Office website was designed to provide professional and empathetic information to support people in difficult life situations. The site...
WordPress support & development in Budapest
Need this service: Astro developer in Budapest?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
WCAG 2.2, BFSG, EAA conformance report and remediation backlog.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Custom WordPress engineering and architecture.
Clearer structure, messaging, and conversion flow.
Core Web Vitals, caching, and faster delivery.
NIS2 and DORA scope mapping, supplier register, incident runbook.
Related categories
Supporting articles

Germany's Barrierefreiheitsstärkungsgesetz applied from 28 June 2025. It transposes EAA Directive 2019/882 into national law. I unpack how it affects WooCommerce stores in DE and the four plugin failure patterns I see in audits.

WCAG 2.2 was first published as a W3C Recommendation on 2023-10-05; the current published version on www.w3.org/TR/WCAG22/ is dated 2024-12-12. The EU Accessibility Act (Directive 2019/882) applies from 2025-06-28. Germany's Barrierefreiheitsstärkungsgesetz transposes it into federal law on the same date. This article is the implementation map for a WordPress site in 2026.

BFSG and the EU Accessibility Act require a published accessibility statement with a working complaint mechanism, not just a compliant front end. This is a copy-ready template structure mapped to EN 301 549 clauses and WordPress deliverables.