The plugin problem and what it costs you

Nobody sets out to build a website with eleven subscriptions attached to it. It happens the way most expensive things happen — one reasonable decision at a time.

You need a newsletter, so you add an email tool. You want reviews on your product pages, so you add a reviews app. Customers keep emailing to book, so you add a scheduling tool. The contact form needs a field the theme doesn't have, so you add a form builder. Each one solves a real problem on the day you install it. None of them is a bad decision in isolation. And two years later you're paying for a stack that costs more than your platform does and nobody can tell you what half of it is for.

We spent years supporting stores in exactly that state. This is what we learned about counting the real cost — and what changes when the answer isn't another install.

The costs that don't appear on the invoice

The subscription is the visible cost and usually the smallest. Four others do more damage.

Weight

Nearly every add-on works by injecting its own code into your pages — scripts, stylesheets, fonts, sometimes a small framework of its own. A review widget that renders a row of stars can easily cost a few hundred kilobytes and a render-blocking request. Ten of those and your site is slow in a way no single one of them caused.

This is the cost merchants notice last and pay for most, because it lands squarely on conversion. Our page speed guide covers what that actually costs you in sales.

Seams

An add-on is written to work on thousands of different sites, which means it can't be written to match yours. So it approximates — nearly your font, nearly your button shape, nearly your spacing. Individually each is a small wrongness. Collectively they are the difference between a site that feels designed and a site that feels assembled, and customers read that difference as a signal about your business whether or not they could name it.

Fragility

Every add-on is a moving part maintained by someone else, on their schedule, with their priorities. They update. They conflict. They get acquired and repriced. Occasionally they're abandoned, and you discover this when something quietly stops working. The more of them you have, the more often something is broken and the harder it is to work out which one did it.

Support gaps

This one is subtle and infuriating. When your booking flow breaks and three vendors are involved, each will — politely and often correctly — tell you it's someone else's problem. You become the integration engineer for a system you didn't design and can't see inside. We've watched merchants lose a week to this and end up fixing it by removing something rather than repairing it.

The real cost of an add-on isn't $19 a month. It's $19 a month, plus a slower site, plus a visible seam, plus one more thing that can break on a Saturday.

How to audit a stack you already have

If you're running a site with a pile of add-ons today, this is the exercise. It takes an afternoon and it's worth it whatever platform you're on.

1. List everything, with its price

Open your billing and write down every recurring charge connected to your website — platform, hosting, email, apps, plugins, domains, SSL if you pay for it, backup services, form tools, anything. Add it up and annualise it. That number is almost always larger than people expect, and it's the number to compare against, not the platform fee.

2. Ask what each one is for — out loud

For every line, answer: what does this do, and what would break tomorrow if I removed it? If you can't answer, you've found your first cancellation. Add-ons installed for a campaign that ended, or by someone who no longer works with you, are the most common finding.

3. Look for overlap

Two things collecting email addresses. A popup tool and a form tool. A reviews app and a testimonials section. Overlap is where the easy savings are, and it's also where the confusing bugs come from, because two tools are writing to the same part of the page.

4. Weigh what's left against what it costs

Test your site's load time, then disable one heavy add-on and test again. Do that for each of the big ones. Some will turn out to cost you almost nothing; a couple will be responsible for most of the weight. Now you can make an informed trade instead of a guess: is this feature worth this much of my speed?

5. Cancel, don't just deactivate

Deactivated tools often leave code behind and always keep billing. Remove them properly, then check your pages afterwards for the leftovers — orphaned markup, empty containers, a stylesheet still loading for a widget that's gone.

The other model: nothing to install

We built Tropic Arts the other way round. The features most businesses reach for add-ons to get are simply part of the platform: the blog, the newsletter and email campaigns, appointments and online booking, the customer list and inbox, locations and maps, site search, SEO controls, and — on the Store plan — products and inventory, cart and Stripe checkout, orders and fulfilment, shipping, sales tax, refunds, subscriptions and customer reviews.

All of it renders in your template's own type and colours, because it's built from the same components as the rest of your site. There's no widget to style, no script to inject, and no second vendor to email when something's wrong. One bill, one login, one place where the answer is.

And there's no plugin marketplace, which is the point — and also the cost.

What you give up

We'd be doing exactly what we're criticising if we pretended this trade only goes one way. An ecosystem of thousands of add-ons has a real advantage: someone has probably already built the specific thing you need.

On our platform, if we haven't built it, you can't install your way to it. A niche loyalty programme, a particular warehouse integration, a specific accounting sync — you ask us, and you wait, and sometimes the answer is that it isn't on the roadmap. If your business genuinely depends on a specialised integration, an open ecosystem is the better fit and you should choose it.

What we'd say is that the trade is symmetrical. The reason your site can't gain a badly-styled third-party widget is the same reason you can't install one. Whether that's a good deal depends entirely on how unusual your requirements are — and most businesses are less unusual than they think.

The arithmetic, honestly

Here's the comparison we'd actually run. Take your current annual total from step 1 above. Against it, put a Tropic Arts plan: $29 a month for a site without an online store, $39 with one, month-to-month, no setup fee. Hosting, SSL, daily backups, a global CDN and unlimited pages and bandwidth are included, as are 5,000 emails a month. Every template is included on every plan. If you sell, there's a 1.1% platform fee on online sales and subscription invoices, and Stripe bills its own processing rates directly to you.

Then add the line most comparisons leave out: the hours. Whatever you or someone you pay spends each month keeping a stack of tools compatible with each other is a real cost, and for a lot of small businesses it's the largest one on the page.

Do that sum for your business rather than for a hypothetical one. Sometimes an assembled stack genuinely wins — if you're already running well and the pieces aren't fighting, the migration isn't worth it. But run the numbers before you assume.

---

One principle, either way

Whatever platform you're on: every tool you add should earn its place, and be reviewed once a year. Nothing installs itself, but plenty of things stay long after they've stopped being useful, quietly charging you and quietly slowing you down.

The best-run small sites we've seen aren't the ones with the most capability bolted on. They're the ones where every part is there on purpose, and the owner can tell you why.