Cintesi eCommerce website project

Cintesi: why an online store needs ongoing performance work

A website launch isn't the finish line, especially for an online store. How ongoing ecommerce performance optimisation keeps Cintesi's BigCommerce B2B store fast.

A website launch isn’t the finish line. For an online store it’s more like the start of a race: products change, prices change, campaigns come and go, and every new app, image and script can slowly make the site heavier. That’s why ecommerce performance optimisation is ongoing work.

Key points

  • Cintesi‘s store runs on BigCommerce B2B Edition with a custom theme and Accredo integration
  • Feature-rich stores slow down over time as images, apps and products pile up
  • We measure key pages regularly and fix slowdowns before customers notice
  • Most slow stores can be sped up without a rebuild
Cintesi BigCommerce B2B ecommerce website on a laptop and phone
Cintesi’s retail and wholesale store.

What we built for Cintesi

Cintesi online store showing product categories and furniture ranges

Cintesi’s store runs on BigCommerce B2B Edition with a custom theme we designed and built. It serves two very different customers:

  • Retail customers get a streamlined shopping journey, wishlists and quick-shop.
  • Wholesale customers apply through a trade flow, then get wholesale pricing, company accounts with multiple buyers, a trade dashboard, saved products, repeat-purchase shortcuts and quotes.
Cintesi store on laptop and tablet, connected to the Accredo business system

Connected to Accredo

Our middleware connects BigCommerce to Cintesi’s Accredo system. Accredo stays the source of truth, and products, customers, pricing, stock, images, categories and orders sync between the two, so the team isn’t keeping two systems in step by hand.

The storefront also includes promotion tiles, colour and material swatches, smart categories, a dynamic menu, AI-powered search and a blog split into Spaces and Stories.

Why performance is never done

A feature-rich store has a lot going on. Over time, a few things tend to creep in:

Bigger images

Product photos uploaded straight from a camera or supplier, far larger than the page needs.

More apps and scripts

Marketing, reviews and chat tools, each adding code to every page.

More products and filters

Category pages that grow heavier as the catalogue grows.

Third-party slowdowns

External services that slow down on busy days and hold up the page.

None of these is a problem on its own. Together they can quietly add seconds to every page, and slow pages cost sales, especially on mobile.

What ongoing optimisation looks like

What we doWhy it matters
Measure key pages (home, category, product, checkout) on mobile and desktopSlowdowns are caught early, not after sales drop
Image discipline: modern formats, sensible sizes, lazy loadingImages are usually the biggest part of a page
Script reviews: remove unused apps, load the rest only where neededLess code to download and run on every page
Integration health checks on syncs with systems like AccredoStock and pricing stay accurate without slowing the storefront
Small, steady layout, search and navigation improvementsBased on how customers actually shop

Frequently asked questions

Why does an online store get slower over time?

Larger images, extra apps and scripts, growing catalogues and third-party services all add weight. Each is small, but together they can add seconds to every page.

Do I need a rebuild to make my store faster?

Usually not. Most slow stores can be sped up by fixing images, removing unused apps and loading scripts only where they’re needed.

Can ecommerce sync with Accredo without slowing the site?

Yes. With middleware handling the sync in the background, the storefront stays fast while products, stock, pricing and orders stay in step with Accredo.

Is your store getting slower?

If your online store felt fast at launch and doesn’t any more, it’s usually fixable without a rebuild. We’ll show you where the time is going.

Get a store performance checkRead the Cintesi case study