Describe the problem in your own words. AI picks the services, solutions and articles on our site that fit it.

    New store frontend

    A new theme on your current platform, or a separate front end when a theme isn't enough

    For most stores a new theme fixes speed and looks. We build a headless front end when the catalogue, traffic or number of channels outgrow what a theme can handle.

    Tell us about your store
    How it works

    How we decide and build

    We decide from your store's data, not from trends.

    1. 1Decision: theme or headlessWe look at catalogue size, traffic, markets and languages, and what's holding the current theme back. The recommendation follows from that.
    2. 2New themeWe build a theme from scratch or on a lean base, without plugins that load on every page. Your team keeps editing content in the admin.
    3. 3Headless front endA separate app, for example in Next.js or Nuxt, pulls products and the cart from the store via API. The platform stays as the order back end.
    4. 4Testing on a store copyWe test the new front end on a copy with real products and test payments before any customer sees it.
    When it makes sense

    Signs your current theme needs replacing

    Tweaks stopped helping

    Image optimisation and caching barely move the needle because the theme loads dozens of scripts on every page.

    Plugin on top of plugin

    Every new feature is another plugin, and updating one breaks another.

    A big catalogue slows listings

    With tens of thousands of products, filters and search keep getting slower.

    Several markets and channels

    One catalogue has to feed the store, an app and several markets, and the theme only handles one store.
    On your platform

    Themes and headless on six platforms

    Every platform can take a new theme. Headless makes sense where the platform has a good API.

    Shopify

    A new Online Store 2.0 theme or a headless front end on the Storefront API. Checkout stays on Shopify.

    WooCommerce

    A lean theme without page builders, or a headless front end pulling data over the REST API.

    PrestaShop

    A new template with tidied-up modules. Headless is possible but takes more API work.

    Shopware

    A new theme or a headless front end on the Store API, which Shopware uses in its own products too.

    IdoSell

    A new look within the template and admin settings. Headless is assessed case by case against the available API.

    Shoper

    A new template and Shoper App Store apps. We'll say what headless allows once we've looked at your store's API.
    Results

    How we check the results

    We measure the same pages before and after, on mobile and in Google Analytics.

    1. 1LCP on the product page
    2. 2INP on the filtered listing
    3. 3Mobile conversion rate
    4. 4Number of plugins and scripts

    We compare the same pages under the same conditions.

    FAQ

    Common questions

    How do you know a new theme is enough?

    From measurements. If plugins and scripts slow the current theme down, a new theme solves it for less than headless.

    Is headless more expensive to run?

    Yes, because there's a separate app to host and update. That's why we only recommend it when a theme really won't do.

    Can our team still change banners and content?

    Yes. With a theme, in the store admin; with headless, in the store admin or a content system connected to the front end.

    What happens to the plugins we use today?

    We review each one. Some get replaced by theme code, some stay, and some turn out to be unnecessary.

    Let's talk

    Tell us about your store

    Share your store's address, platform and number of products, and what bothers you most today. We reply within one business day.

    New store frontend

    Other parts of this service

    Checkout audit

    We measure mobile speed in PageSpeed Insights (LCP, INP, CLS), walk through the product page, cart and payment, and use Google Analytics to find the step where shoppers drop off.
    I want to know more

    Mobile-first design

    Home page, product list, product page and cart, designed for the phone screen first. You approve the design before we write code.
    I want to know more

    A faster checkout

    Guest checkout, address autocomplete, a parcel-locker map in the cart, delivery cost shown on the product page, and BLIK, Apple Pay and Google Pay on the first payment screen.
    I want to know more

    Launch without a sales break

    We test the new frontend on a copy of the store and switch over in the quietest hour. The old theme stays ready to restore.
    I want to know more
    See the whole service