Migrate from WordPress to Astro in Brno
Many businesses in Brno 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.
Brno is the deep-tech, open-source engineering, and scientific instruments capital of Moravia and the Czech Republic. Across the software, Linux, and cybersecurity R&D centers at Česká technologická park (Brno Technology Park) near VUT (Brno University of Technology) in Královo Pole, the startup incubator at JIC (Jihomoravské inovační centrum), the enterprise campuses along Spielberk Office Centre and Vlněna in Trnitá, and the world-renowned electron microscopy and space-tech manufacturers in Řečkovice, Medlánky, and Černovice, engineering teams ship technical products to global markets. I build and migrate fast, maintainable web platforms using Astro, working as a solo software developer in Gdynia, Poland, collaborating with your Brno team entirely in writing.
Why Brno SaaS, cybersecurity, and hardware engineering teams choose Astro
Brno’s technology sector is built by engineers who care about clean architecture, fast build pipelines, and low runtime overhead. Yet many Brno companies still run their public marketing websites, product catalogs, and documentation portals on either legacy monolithic WordPress installs or heavy React Single-Page Applications (Next.js / Gatsby) that ship hundreds of kilobytes of unnecessary client-side JavaScript on every page view.
Astro is designed specifically for content-driven, technical web platforms:
- Zero JavaScript by default: Astro compiles
.astro, Markdown, and MDX templates into pure, semantic HTML and scoped CSS at build time. - Astro Starlight & Content Layer for developer docs: For Brno software houses, API platforms, and scientific equipment vendors, Astro Starlight and the Astro Content Layer API (
src/content.config.ts) turn thousands of MDX documentation pages, OpenAPI specifications, and hardware datasheets into a type-safe, searchable static site with built-in Pagefind search that runs without a paid third-party search subscription. - Selective hydration via Astro Islands: When a page needs an interactive React, Vue, or Svelte component, such as a SaaS tier calculator, an electron-microscope configuration selector, or a live code sandbox, Astro hydrates only that isolated island (
client:visibleorclient:idle).
---
// src/pages/cs/dokumentace/[...slug].astro
import { getEntry, render } from 'astro:content';
import DocsLayout from '../../../layouts/DocsLayout.astro';
import ApiSandbox from '../../../components/react/ApiSandbox.tsx';
const { slug } = Astro.params;
const doc = await getEntry('docsCs', slug);
const { Content, headings } = await render(doc);
---
<DocsLayout title={doc.data.title} description={doc.data.description} headings={headings} lang="cs">
<!-- Pure static HTML compiled from MDX: 0 KB client JS -->
<Content />
<!-- Interactive React Island hydrated only when scrolled into view -->
{doc.data.interactiveEndpoint && (
<ApiSandbox client:visible endpoint={doc.data.interactiveEndpoint} locale="cs-CZ" />
)}
</DocsLayout>By keeping the main thread free of global virtual-DOM hydration, this architecture targets Google’s official Core Web Vitals “Good” thresholds in real-user field telemetry:
- 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
Dual-engine SEO in Czechia: Google and Seznam.cz (SeznamBot)
While Brno SaaS and microscopy exporters acquire international leads primarily through Google (en, de-DE, de-AT), domestic B2B and consumer traffic in the Czech Republic splits between Google and Seznam.cz.
Unlike Googlebot’s evergreen Chromium rendering queue, SeznamBot relies much more heavily on the initial server-rendered HTML document and struggles when canonical tags, structured data, or body copy are injected client-side via React hydration. Because Astro outputs complete, deterministic HTML, <link rel="canonical">, reciprocal hreflang links (cs, en, de, sk, x-default), Open Graph tags, and server-rendered Schema.org JSON-LD @graph blocks directly at build time, your pages index cleanly in both Seznam.cz and Google from day one.
Czech statutory and regulatory compliance built into your Brno Astro site
A commercial website operated by a Czech společnost s ručením omezeným (s.r.o.) or akciová společnost (a.s.) headquartered in Brno must comply with specific Czech legislation published in Sbírka zákonů alongside European Union regulations.
1. ÚOOÚ (Act No. 110/2019 Sb.) and ZEK § 89(3) strict opt-in cookie consent
In the Czech Republic, personal data protection is governed by the GDPR and Act No. 110/2019 Coll., on Personal Data Processing (Zákon č. 110/2019 Sb., o zpracování osobních údajů), enforced by the Office for Personal Data Protection (Úřad pro ochranu osobních údajů - ÚOOÚ).
Since 1 January 2022, § 89(3) of Act No. 127/2005 Coll., on Electronic Communications (Zákon o elektronických komunikacích - ZEK) enforces a strict opt-in regime for storing or accessing any non-technical data on a visitor’s device. In my Astro builds for Brno businesses:
- Zero non-essential scripts before affirmative consent: Whether you use Google Analytics 4, Seznam Sklik retargeting, or PostHog, non-technical scripts remain completely inert in the static HTML until the visitor explicitly opts in via your Consent Management Platform (including Google Consent Mode v2 and Seznam CMP signals).
- Self-hosted
.woff2web fonts: I remove all external calls to US font CDNs (fonts.googleapis.com) and self-host subsetted.woff2fonts with full Czech diacritics (ě, š, č, ř, ž, ý, á, í, é, ú, ů, ď, ť, ň) directly from your first-party European origin.
2. Mandatory corporate disclosures under § 435 of the Czech Civil Code (Krajský soud v Brně)
Under § 435 of Act No. 89/2012 Coll., the Civil Code (Občanský zákoník) and Act No. 90/2012 Coll., on Commercial Companies and Cooperatives (Zákon o obchodních korporacích - ZOK), every Czech business must publish specific identification data on its website.
I wire a schema-validated global footer and legal layout that renders server-side across all language versions:
- Registered company name (Obchodní firma) and legal form (s.r.o., a.s.).
- Registered seat (Sídlo) in Brno (e.g., Brno - Královo Pole, Brno-střed, Žabovřesky, or Slatina).
- 8-digit Identification Number (IČO - Identifikační číslo osoby) and VAT ID (DIČ,
CZ...). - Commercial Register entry: Společnost zapsaná v obchodním rejstříku vedeném Krajským soudem v Brně, oddíl C (or B), vložka XXXXX.
- For consumer e-commerce platforms, mandatory pre-contractual disclosures and out-of-court dispute resolution information (Česká obchodní inspekce - ČOI,
coi.cz) under Act No. 634/1992 Coll., on Consumer Protection (Zákon o ochraně spotřebitele).
3. Czech Accessibility Act (Zákon č. 424/2023 Sb.) and Cyber Security (NÚKIB)
Czechia transposed the European Accessibility Act through Act No. 424/2023 Coll., on Accessibility Requirements for Certain Products and Services (Zákon č. 424/2023 Sb., o požadavcích na přístupnost některých výrobků a služeb), effective from 28 June 2025. In addition, Brno is the headquarters of the National Cyber and Information Security Agency (NÚKIB - Národní úřad pro kybernetickou a informační bezpečnost), which oversees the Czech transposition of NIS2 (Zákon o kybernetické bezpečnosti).
Building your public web platform on Astro directly supports both frameworks:
- WCAG 2.1 Level AA / EN 301 549 accessibility: Every Astro template uses semantic HTML5 landmarks (
<header>,<nav>,<main>,<article>,<footer>), native<details>/<summary>accordions, and keyboard-accessible Astro Islands with clear:focus-visiblestates. - Hardened surface area: By compiling public pages to static HTML on edge CDNs and isolating any headless CMS or ERP backend on a private network, your public website has no SQL database or
/wp-adminlogin surface exposed to automated attacks.
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 Brno. When you hire me, you work directly with the engineer writing your Astro and TypeScript code: no account managers, no agency overhead, and no junior handoffs.
- Asynchronous written engineering for Brno teams: I work without phone calls, video meetings, or live workshops. Every requirement, route mapping spreadsheet, schema definition, and pull request review happens in writing via email, GitHub/GitLab issues, or Linear/Jira. Your Brno developers and product owners get a precise, searchable written record they can review asynchronously.
- UI design handoff for Brno projects: Graphic design, brand assets, and wireframes come from your Brno designer or studio. Your in-house designer or Brno design studio provides 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 Brno team sends to start:
- Your existing domain URL (for a migration) or a written functional brief (for a new build).
- Read access to your Brno Figma workspace or existing Git repository.
- Your preferred content workflow (Markdown/MDX in Git, Sanity, Strapi, Directus, Storyblok, Contentful, or headless WordPress) and target locales (
cs,en,de). - Any required form, API, or CRM endpoints.
I reply in writing on working days and deploy every milestone to a private staging URL so you can verify Core Web Vitals, Seznam/Google SEO tags, and Czech statutory disclosures before production cutover.
Start your Astro project in Brno
Integrating Brno Open-Source Workflows, CI/CD Pipelines, and Headless APIs
Brno engineering teams frequently maintain strict GitLab CI or GitHub Actions pipelines alongside self-hosted Keycloak authentication, OpenAPI / Swagger specifications, and headless CMS instances (Strapi, Directus, Sanity, or Storyblok). When I architect your Brno Astro repository, I set up automated TypeScript (astro check), Playwright accessibility checks, and Pagefind static indexing inside your CI pipeline so your internal developers can push MDX documentation or product updates with zero friction.
If you want to launch a fast Astro website, build a Starlight documentation portal, or migrate an existing Brno platform from WordPress, Webflow, or Next.js, send me your current URL, target languages, CMS preference, and timeline via my contact page. Your initial written Brno architecture scope is free, and I reply in writing on working days.
Selected projects
Examples of my work.
Media & Publishing: satyr.pl
satyr.pl was a Polish satirical and adult-humour website from 2000-2015, built around WordPress publishing, multimedia, comments, ratings and performance work.
merkam.eu - WordPress Project | WPPoland
The merkam.eu website was designed for a manufacturer of kitchen countertops made from granite, conglomerate, and marble. The site's purpose is to showcase the product offering, gallery of completed projects, and generate inquiries from clients interested in modern kitchen solutions.
Native mobile apps using JavaScript - Tabris.js
Tabris.js is a modern framework that enables the creation of native mobile apps from a single codebase using JavaScript or TypeScript. This solution allows d...
WordPress support & development in Brno
Need this service: Astro developer in Brno?
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.