HEADLESS · WORDPRESS + NEXT.JS
Keep managing pages, blog posts and images in WordPress. I build your frontend with Next.js for your business website or WooCommerce shop. Design and features are agreed around your project, with a focus on fast loading and workflows that fit your business.
FOR WEBSITES AND SHOPS
For business websites, magazines and multilingual sites: your team creates content in WordPress. The new frontend presents it through custom pages and components. Design and interaction are developed independently of the previous theme or page builder.
For shops with individual requirements: WooCommerce manages products and orders. In your own frontend, we shape product search, variant selection, cart and checkout around your customers. Existing integrations are included in the planning.
We first examine where your existing site hits its limits. If targeted optimization is enough, that is the approach I recommend.
HOW THE SYSTEMS WORK TOGETHER
Your content. Your website.
WordPress for your content. WooCommerce when you need a shop.
Pages, navigation and interactions are custom-built. The frontend loads its own components instead of the previous theme and page-builder files.
Keep managing pages, blog posts and images in WordPress. An API delivers the content to the frontend. Editable components and previews are planned around your editorial workflow.
WooCommerce manages products, prices and orders. Required plugins and integrations remain part of the system. Payments, shipping and ERP connections are reviewed before implementation.
A REAL CLIENT PROJECT
Visit live shop ↗ROC Sports received a Next.js storefront connected to WooCommerce, JTL-Wawi and Stripe. Blog posts are also created in WordPress and displayed in the custom frontend. The shop launched on 10 September 2026 with 101 products.
Historical measurement: mobile Lighthouse 97–99, measured on 15 September 2026. Results depend on the page, test conditions and system state.
OPEN. EXPLORE. TRY IT.
formraum.WORDPRESS WEBSITE + JOURNAL
Explore a fictional interior studio with a custom Next.js website. Its journal articles are loaded from WordPress — open a story and see how familiar content management meets individual design.
Explore the website demo ↗MAISON is a fictional fashion brand. Explore the same eight products in two carefully designed stores — including sizes, search, filters, wishlists, a bag and a simulated checkout.
A custom shopping experience with a cart drawer and a checkout built for this demo.
Explore demo →
An Elementor storefront with FiboSearch, YITH filters and wishlist, page caching, and the native WooCommerce cart and checkout. The final purchase remains a simulation.
Explore demo →Both are demo projects, not client references. No real orders or payments. Both use the same WooCommerce backend with eight products. Carts and wishlists are separate for each demo. This small catalog is not representative of every production shop.
MEASURED ON 10 OCTOBER 2026
How soon can you see the change? In these demos, the Next.js frontend responded faster when adding, updating and removing a product. The checkout was also ready sooner. Try the journey yourself.
| Action | Next.js | WordPress |
|---|---|---|
| Add to cart | 2.04 s | 2.44 s |
| Change quantity from 1 to 2 | 1.19 s | 2.27 s |
| Remove product | 0.61 s | 1.35 s |
| Open checkout until it is ready | 2.60 s | 5.18 s |
| Page | Next.js | WordPress |
|---|---|---|
| Homepage | 97 | 74 |
| Product page | 99 | 78 |
Interaction times and Lighthouse measure different things. These results apply to these demos, not every website. We assess the benefit of a custom frontend for your project using your own system.
Interactions: Chrome, fresh guest sessions, 390 × 950 pixels, without artificial network or CPU throttling. Three complete journeys with Wool Coat Camel in size M. Measured from the click until the visible update is complete. Next.js uses a cart drawer; WordPress opens a native cart page. Both use the same WooCommerce backend with eight products.
Lighthouse 13.5.0 with the standard mobile profile, run sequentially on the same computer: Next.js after image optimization, using the median of three runs (homepage 96–97, product page 97–100); WordPress using one run. Interaction times come from the earlier comparison that day; the subsequent Next.js change concerns image delivery. This is a documented snapshot, not proof of a universal architecture advantage.
WordPress uses Elementor, ShopLentor product widgets, FiboSearch, YITH filters and wishlist, plus WP Super Cache. Both final purchases are simulations. WooPayments is installed but unconnected, so payment fields are not included in this comparison.
View measurement data (JSON) ↗THE PATH TO YOUR NEW FRONTEND
Review the website, editorial workflow and APIs; for shops, also payments and data flows.
Agree deliverables, boundaries and costs in writing.
Build the frontend and connect the agreed interfaces.
Check content editing, previews and functionality; for shops, also buying journeys.
Explain operations and prepare the launch together.
BEFORE IMPLEMENTATION
In a free 30-minute intro call, we discuss whether optimising the existing system or building a separate frontend is appropriate. The call does not commit you to a paid assessment.
excluding VAT; applicable VAT is specified in the quote
We agree the review scope and required access in advance. I review functionality and integrations, assess headless suitability and define the responsibilities of WordPress or WooCommerce and the new frontend. You receive an implementation concept with a fixed-price quote.
The assessment does not include a complete technical trial of every integration. Additional investigations are quoted separately and start only when commissioned.
If you commission the headless implementation within three months, I credit the full assessment fee. Large shops, custom features and WordPress websites without a shop receive a fixed-price quote after assessment.
Request an intro call ↗WOOCOMMERCE · THE STARTING PACKAGE
The defined starting package applies to a small WooCommerce shop with up to 50 products on an existing design foundation. Large shops and custom projects receive a fixed-price quote after assessment. We review which option fits before quoting.
For a WordPress website without a shop, scope and pricing are agreed individually around your content, pages and features.
USD · applicable taxes specified in the quote
Discuss your scope ↗The written quote specifies which template adaptations are included. A fully bespoke design is quoted as a custom project.
Extensions, ERP, B2B, plugins, custom design and larger migrations are quoted separately. The binding scope is agreed in writing after the system review.
Headless support quoted for the agreed scope.
Headless adds a separate Next.js frontend and APIs alongside WordPress. The service agreement defines the maintenance, updates and development I handle. We agree on the scope and response times before starting. Hosting and server maintenance are not included; they are quoted and billed separately.
GOOD TO KNOW
No. WordPress remains your content management system and WooCommerce your shop administration. I develop the frontend independently with Next.js. We review your system to establish which APIs and extensions are needed.
That is the aim, subject to a technical review. Data flows, interfaces and edge cases are checked before the quote. ERP changes are quoted separately.
If hosting, images, the theme or individual plugins cause the problems, targeted optimization may be the better choice. The analysis first establishes whether a new storefront is needed.
Large shops and custom projects receive a fixed-price quote after assessment. The defined starting package begins at USD 7,500 for one WooCommerce shop with up to 50 products and one design variant based on an existing template. Included adaptations and the binding scope are agreed in writing after the system review; applicable taxes are specified in the quote. A fully bespoke design and additional features are quoted separately. A WordPress website without a shop receives an individual quote.
You receive an introduction to the agreed operation of the site. Optional headless support is quoted for the agreed scope. The service agreement specifies the maintenance, updates and development it covers. We agree on the scope and response times before starting. Hosting and server maintenance are not included; they are quoted and billed separately.
The €59 and €149 monthly plans on my main website cover the WordPress services described there. Headless adds a separate Next.js application and APIs, so its support needs a separate scope. The quote specifies whether any WordPress services are included and which ones.
Yes. You continue creating and editing content in WordPress. The frontend receives it through an API. We agree on editable page components and previews together. ROC Sports already publishes its blog posts this way.
Plugins remain in use for administration, APIs and required features. The new frontend is custom-built and does not automatically load the previous theme, Elementor or widget files. Elementor does not control its presentation. Required APIs still need to respond quickly, so we assess their performance too.
Yes. WordPress can manage the content of a business website, blog or magazine without a shop. Scope and pricing for that frontend are agreed individually; the starting package shown here applies to WooCommerce.
€590 excluding VAT. We agree the review scope and access in advance. You receive a suitability assessment, a review of functionality and integrations and a concept with a fixed-price quote. Complete technical trials of all integrations are not included; additional investigations are commissioned separately. If you commission the headless implementation within three months, I credit the full fee. The free 30-minute intro call does not commit you to a paid assessment.
Enter your shop address and email — you'll instantly see how fast your shop is and get my personal detailed report.
YOUR DIRECT CONTACT
I’m Markus. Send me your website or shop address and describe what is holding you back. We discuss whether targeted optimization is enough or a custom frontend makes sense. You speak directly with the person who builds it.
office@markusstoeger.com