Skip to content
headless.by Markus Stöger

Website and shop demos

OPEN. EXPLORE. TRY IT.

Websites and shops.
Try them yourself.

FORMRAUM: fictional interior studioformraum.

WORDPRESS WEBSITE + JOURNAL

Your content. Your own website.

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 · One collection, two shops

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.

Compare the full journey

  1. Open the coat in both shops and select size M.
  2. Add it to your cart and open the cart.
  3. Change the quantity, remove it, then add it again.
  4. Continue to checkout. The final purchase is a simulation.

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

Loading is only the beginning.

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.

Interaction times · median of three journeys per shop
ActionNext.jsWordPress
Add to cart2.04 s2.44 s
Change quantity from 1 to 21.19 s2.27 s
Remove product0.61 s1.35 s
Open checkout until it is ready2.60 s5.18 s
Lighthouse · mobile performance, 0–100 points
PageNext.jsWordPress
Homepage9774
Product page9978

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.

How we measured

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) ↗
Is headless right for my website? →