Migrate from WordPress to Astro in Paris
Many businesses in Paris 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.
I am Mariusz Szatkowski, a solo web developer based in Gdynia, Poland, and I build Astro sites for companies in Paris and Île-de-France. Three kinds of Paris buyer tend to need what Astro does well: startups on the Station F campus that must launch a bilingual site before their next round, luxury and fashion houses whose lookbooks have to look perfect on a phone in the metro, and enterprise groups around La Défense whose corporate portals must pass a security review and a legal review in the same quarter. Astro compiles pages to HTML ahead of time and sends JavaScript only for the parts that need it, which makes the French legal layer easier to enforce: a script that is not on the page cannot drop a cookie.
Who in Paris actually benefits from Astro
Astro is a content framework. It suits sites where most pages are read rather than operated: marketing pages, editorial collections, documentation, product catalogues, press rooms, investor pages. It suits logged-in dashboards and complex checkouts less well; for those, the Next.js developer page for Paris describes the better fit.
In Paris, that content profile shows up in three very different organisations. Each one cares about speed for its own reason and runs into French law at a different point. A brief from a fifteen-person AI startup and a brief from a fashion house share little beyond the framework.
Station F startups: launch the site before the funding round closes
Station F sits in the former Halle Freyssinet, a freight hall built in 1927 by the engineer Eugène Freyssinet and listed as a historic monument in 2012. Xavier Niel bought the building in 2013, and the campus opened in 2017 at 5 Parvis Alan Turing in the 13th arrondissement. Its own about page says more than 1,000 startups work there each year and describes it as the world’s biggest startup campus.
Founders on a campus like that share a familiar set of website problems:
- The site must exist in French and English from day one, because investors, early customers and hires come from both sides.
- A pricing page, a changelog, a security page and API documentation pile up faster than anyone can maintain them in a page builder.
- Nobody on the team wants to own a CMS server, patch PHP or pay for managed hosting while runway is the constraint.
- The site gets rebuilt every time the positioning shifts, which in the first two years can happen more than once.
Astro answers these with plain files. Pages, changelog entries and docs live as Markdown or MDX in the same repository as the product, validated by a content collection schema written with Zod. If a founder adds a changelog post without a French title or with a date in the wrong format, the build fails and tells them which field is wrong. Documentation can run on Starlight, Astro’s documentation theme, with built-in search and sidebar navigation, while the marketing pages use the startup’s own components.
Hosting follows from the static output. The whole site deploys to Cloudflare Pages or another edge host for less than a managed WordPress plan, with a preview URL on every pull request. When the positioning changes, the rewrite touches templates and copy, not a database migration.
Luxury, fashion and beauty: brand fidelity on a slow phone
In Paris, luxury retail clusters in the Triangle d’Or around avenue Montaigne, along rue du Faubourg Saint-Honoré and in Saint-Germain-des-Prés, with ateliers and showrooms in the Marais. Digital work for these houses runs on a different success criterion than mass-market retail. A conversion uplift that costs the brand its typography or photographic quality is a bad trade, and the brand team will say so.
That makes performance work in this sector mostly an image and font problem:
- Campaign photography arrives as very large files. Astro’s Picture component generates AVIF and WebP variants in several sizes at build time, and the Image component sets width and height so the layout does not shift while the photo loads. Where the mobile crop of a campaign shot must differ from the desktop one, I add it as a separate source in a plain picture element.
- Brand typefaces are often licensed fonts with many weights. I self-host them, subset them to the glyphs the site actually renders in French and English, and preload only the weight used above the fold.
- Lookbooks and collection pages are static. A product carousel or a 360-degree viewer becomes an island hydrated with
client:visible, so its JavaScript downloads only when the visitor scrolls to it. - Page transitions can use Astro’s view transitions, which give the editorial feel brand teams ask for without turning the whole site into a single-page application.
Checkout can stay where it already is. When a house sells through Shopify or another commerce platform, Astro can carry the editorial side (storytelling, store locators, appointment booking at the flagship), read products from the Shopify Storefront API at build time and hand the cart to the commerce platform. The Shopify developer page for Paris covers the checkout side.
Product recommendation blocks on these sites raise the cookie question covered under Article 82 further down this page.
La Défense and Île-de-France enterprise groups
The business district of La Défense, just west of Paris in the Hauts-de-Seine department, holds the head offices of large listed groups, banks, insurers and consultancies. Further out, Île-de-France adds industrial and research clusters such as the Paris-Saclay plateau. Their websites are rarely one site. A typical group runs a corporate portal, an investor relations section, a careers site, several brand or country sites and a press room, all with their own owners.
Astro fits the content half of that estate. Enterprise IT and procurement teams usually ask about four things:
- Attack surface: a static Astro site has no public database and no admin login on the production domain. Editors work in a separate CMS or in Git, and only compiled HTML reaches the edge.
- Document permanence: annual reports and regulated disclosures must stay at stable URLs for years. PDFs live in the repository or object storage with fixed paths, and a redirect map in version control proves that no old address was dropped.
- Security headers: a strict Content Security Policy is far easier to write when the page loads three scripts instead of thirty. I generate the policy together with the build so inline script hashes stay in sync.
- Procurement paperwork: I supply the list of subprocessors (host, form handler, analytics), their locations and their data processing terms, so the data protection officer can review them before go-live.
For groups that keep WordPress as the editorial backend, Astro can read content from the WordPress REST API at build time, which leaves the editors’ workflow untouched. The WordPress developer page for Paris covers projects where WordPress itself stays in front.
French compliance built into the templates
French web projects carry a legal layer that is easiest to get right when the templates are first written. Your lawyer or DPO decides what the documents say. My part is making sure the code does exactly that, on every route, including the landing page someone publishes in a hurry eighteen months after launch.
Cookies and trackers: Article 82 and the Fnac decision
Article 82 of the Loi Informatique et Libertés transposes Article 5(3) of the ePrivacy Directive. Reading or writing information on a visitor’s device requires prior consent, except where it is strictly necessary for a service the user asked for or exists only to carry the communication. The CNIL’s page on what the law says about cookies adds that consent must be free, specific, informed and unambiguous, and that withdrawing it must be as simple as giving it. The CNIL set out its interpretation in guidelines and a recommendation adopted on 17 September 2020.
The Fnac sanction shows what that means for retail. On 22 October 2026 the CNIL fined Fnac Darty Participations et Services 6 million euros and Fnac Direct 1 million euros. Following a complaint from the association noyb, the CNIL had inspected the Fnac mobile app in March 2024. It found that the app sent a user identifier and the products viewed to a third-party domain through an API, to display personalised recommendations and to train the recommendation algorithm, even when users had not consented. The CNIL ruled that personalisation and commercial targeting fall outside the Article 82 exemptions and added a penalty of 10,000 euros per day if the companies did not prove compliance within a month.
The decision concerned an app, but the same pattern exists on many fashion and beauty websites: a “complete the look” or “you may also like” block that calls a vendor API on page load. On an Astro site I handle it like this:
- The product page renders as static HTML with no third-party calls.
- A small consent island stores the visitor’s choice and exposes it to other islands.
- The recommendation block, analytics, advertising pixels and chat widgets mount only after the relevant purpose has been accepted. A refusal means the component never loads, so the request never leaves the browser.
- Strictly necessary storage, such as the basket or the consent choice itself, is kept separate in code and documented in the cookie list your DPO approves.
Forms and data minimisation under the RGPD
The RGPD (Regulation (EU) 2016/679) applies to every contact, appointment and newsletter form. Article 5 limits data to what is necessary for the purpose, and Article 13 requires information at the moment data is collected. In practice I build each form with only the fields the business process uses, put the short information notice next to the submit button with a link to the full policy, and validate submissions on the server with Astro Actions so nothing is trusted from the browser. Where the form posts to a CRM, the retention period your DPO sets is written into the handover document, so whoever maintains the site later knows why records disappear after a given number of months.
LCEN publisher identification after the SREN law
The LCEN (Law 2004-575 of 21 June 2004) requires anyone publishing an online service professionally to identify themselves. The SREN law of 21 May 2024 moved this duty into a new Article 1-1, in force since 23 May 2024. It covers the publisher’s identity and registration details, the name of the director of publication and the name and contact details of the host. Legal notice templates written before May 2024 cite the previous article.
I keep those details in one typed company record (legal name, legal form, share capital, registered office, RCS and SIREN numbers, VAT number, director of publication, host). The legal notice page and the footer read from that record, so a new landing page cannot ship with a stale host address after a hosting move.
French first: the Loi Toubon
Article 2 of Law 94-665 of 4 August 1994, known as the Loi Toubon, makes French mandatory in the designation, offer, presentation and instructions for use of goods and services. For an international brand selling in France, the English site cannot be the only complete one. With Astro’s i18n routing, I make French the default locale and fail the build if a product page, form label, error message or button text exists in English but not in French. English routes are generated from the same content entries and linked with hreflang pairs checked at build time.
Accessibility
Article 47 of Law 2005-102 requires public bodies and companies above a turnover threshold set by decree to make their online services accessible, measured against the RGAA published on accessibilite.numerique.gouv.fr. The European Accessibility Act (Directive (EU) 2019/882) separately applies to e-commerce services provided to consumers after 28 June 2025. Which regime applies to your company is a question for counsel. On the build side, I write semantic landmarks, a correct heading order, labelled form controls, visible focus states and text alternatives into the components themselves, because adding them later to a finished design costs far more.
How French requirements map to Astro features
| Requirement | Where it comes from | How the Astro build handles it |
|---|---|---|
| No tracker before consent | Article 82, Loi Informatique et Libertés | Third-party scripts live in islands that mount only after an accepted purpose |
| Collect only what is needed | RGPD Article 5 | Minimal form fields, server validation with Astro Actions |
| Publisher identification | LCEN Article 1-1 | One typed company record feeds the footer and legal notice |
| French in the offer and presentation | Loi Toubon Article 2 | French default locale, build fails on missing French strings |
| Accessible online services | Law 2005-102 Article 47, EAA | Semantic components, focus and label checks in CI |
Working with me from Gdynia
I work alone and remotely. Paris and Gdynia are both on Central European Time, so a question sent from an office in the 8th arrondissement at 10:00 arrives at 10:00 my time too. I do not travel for workshops or meetings. Every decision is written down, so a brief that passes through brand, legal, IT and procurement before approval never depends on someone’s memory of a call.
A typical engagement runs like this:
- You send the brief: the current URL if there is one, the languages that must be live at launch, the integrations, and the date after which production must not change.
- I reply with written questions and a list of assumptions and risks, including anything legal that your counsel should confirm.
- Once the scope is settled, you receive a written quote. Pricing is individual and depends on templates, languages, integrations and migration volume.
- Work proceeds in milestones, each ending with a staging URL your team can review and forward internally.
- Before launch I hand over the repository, the redirect map if anything moved, the cookie and subprocessor list, and a short maintenance note.
Related services in Paris
- Next.js to Astro migration in Paris if you already run a React site and want to cut its client-side JavaScript.
- Next.js developer in Paris if the project is closer to an application with accounts and live state.
- PHP developer in Paris if a Laravel or Symfony API sits behind the Astro frontend.
- WordPress developer in Paris if editors must keep working in WordPress.
- Astro development for the general service description outside the Paris context.
Send a brief
Use the contact form and include your current URL, the languages you need at launch, your integrations and any fixed dates, such as a collection launch or a results publication. I answer in writing on working days with questions or a scope outline, and the quote follows once the brief is complete enough to price without guessing.
Selected projects
Examples of my work.
Corporate Website: strefapremium.pl
The website strefapremium.pl has been designed as a modern premium portal, dedicated to users seeking exclusive content and services. The site combines high-...
Corporate Website: weglopex.pl
The site weglopex.pl was created as a modern information portal, dedicated to enthusiasts and professionals in the energy industry, with particular focus on ...
Customer Experience Platform: QUALITY WATCH
QUALITY WATCH is a customer experience and service-quality platform presenting mystery shopping, service audits, customer journey work and B2B consulting services.
WordPress support & development in Paris
Need this service: Astro developer in Paris?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
Migration to Astro, Next.js, and headless WordPress.
WooCommerce sync with ERP and wholesale systems.
Business process automation around WordPress and company systems.
Library of concrete automation use cases.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Related categories
Supporting articles

Six to sixteen weeks for typical engagements, with a four-phase shape: discovery, scoping, build and cutover, tuning. The variables are catalogue size, integration count, URL preservation, and editorial team readiness, not framework choice.

A definitive 4-year Total Cost of Ownership (TCO) analysis, real-world Core Web Vitals benchmarks, Astro 7 GraphQL APQ architecture, and a 10-point executive decision matrix for choosing between decoupled and traditional WordPress.

The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.