If a product page feels slow when the customizer loads, this guide explains why and what to check. It is written for merchants who want to understand where the time goes and rule out a stuck customizer. Compare the same product and workflow before attributing the delay to a network, theme, or Composerie.
How the customizer is built to stay fast
Composerie is designed to add as little weight to your store as possible. How much it adds depends on the storefront mode of the product.
Linked does not load a shopper editor through the product loader. The app embed can still add configuration, preconnect hints, and cart integration, so Linked is not a promise of zero Composerie code, markup, or requests on the whole page.
Products in a visible mode (Embedded or Full page) load the storefront integration without blocking the initial page render. The editor runtime is loaded for the customer experience that is actually in use, so the product page can become visible while the customizer finishes loading.
Concurrent mapping loads share a request. Each new sequential load revalidates the mapping, and stored responses are tied to a specific publication revision. A reload is not governed by a fixed 60-second browser cache, and cached content does not guarantee an instant response.
Each mapping request has a five-second timeout. That bounds this request; it does not bound image processing, other requests, or browser rendering, and it does not prove that a lasting hang is outside Composerie.
What to check when a page feels slow
Work through these checks in order. They separate a slow connection or a heavy theme from an actual customizer problem.
Hard refresh the page once
Do a hard refresh to clear a stale cache and force fresh files. On Windows press Ctrl plus Shift plus R. On a Mac press Cmd plus Shift plus R. If the page is fast on the second, normal load, the first load was just warming the cache and the session is now primed.
Test on a different network or device
Open the same product page on another connection, for example mobile data instead of wifi, or on a different device. A difference helps narrow the investigation; it does not identify a single cause by itself.
Check for other apps or a heavy theme
Other storefront apps, large hero images, and heavy theme scripts all compete for the same page load. To test this, duplicate your theme, switch the copy to a clean default theme, and load a customizable product on it. If the page is fast on the default theme, the slowdown is coming from your live theme or another app, not Composerie. See theme compatibility and supported themes for what we test against.
If the customizer never appears, treat it as a load failure
A page that is merely slow will still show the customizer once it finishes. A page where the customizer never shows up is a different problem. Follow the customizer not appearing guide instead of this one.
Frequently asked questions
Does Composerie slow down all my product pages?
The work depends on the display mode and enabled integration. Linked does not load a shopper editor through the product loader, but the app embed and cart integration can still contribute to the page. Measure the actual storefront.
The customizer takes a while to appear on the first visit. Is that normal?
A first visit can load more resources than a later one. Mapping loads still revalidate on subsequent requests. Compare timings and report persistent or excessive delays.
The page seems to hang on the customizer. What is happening?
The five-second mapping timeout only limits that request. Record which part hangs and compare the same product on another browser or theme preview; include those observations when contacting support.
I changed a setting but the storefront still looks the same.
First check that the intended publication update succeeded. Saving alone does not change the storefront. See the changes not showing guide before treating it as a cache problem.
If none of these checks resolve the slowdown, gather the product URL and the browser you tested with, then contact support.
Next: if a setting you changed has not shown up yet, read changes not showing.