Your Website Is Not a Miata. Stop Tinkering.

Brian Christie, growth strategist at Rocket Web Designer Brian Christie · · 7 min read
Mechanics working together in a busy auto repair shop

I restore an old Miata on weekends. It’s a project car, which means it’s never finished, and that’s fine, the point is the tinkering. Your business website is not a project car.

The point is not the tinkering. The point is converting visitors into customers, and every hour you spend adjusting something that already works is an hour you’re not spending on something that doesn’t.

Works ≠ done

A lot of owners treat “it works” as the finish line. The form submits. The site loads. Good enough, move on to something more interesting. But works and done are not the same claim. Works means nothing broke the last time someone tried it. Done means you actually know it converts, it’s fast, and it’s not quietly costing you leads while it sits there looking fine.

Most of the sites I get called in on are not broken in any way an owner would notice by looking at them. They’re just slowly leaking performance, one unchecked plugin and one oversized image at a time, and nobody looks closely enough to catch it because the site “works.”

The pattern I see constantly

Owner redesigns the homepage for the third time this year. Nothing was wrong with the last version, it just didn’t feel fresh enough. Meanwhile the contact form hasn’t been tested in six months, there are 14 plugins active that do what 3 lines of code would handle, and the 800-pixel logo is being rendered at 88 pixels, loading a file ten times larger than it needs to be.

That last one genuinely happened this week. An image file north of four megabytes, straight off a phone camera, displayed as an 88 pixel logo in the header. Every visitor downloaded the full four megabytes just to see a logo the size of a postage stamp, on every single page, on every visit. This is held together with tape and hope.

Symptoms of a site that’s tinkered, not maintained

  • Forms that “should” work but nobody has actually tested since launch.
  • Plugins installed for one feature, still running a year after that feature was abandoned.
  • Images uploaded at full camera resolution, resized only in the browser instead of on the server.
  • A homepage redesigned on a feeling, not on any data about what visitors actually do.
  • A checkout or lead form nobody on staff has submitted themselves in months.

What actually breaks quietly

The failures that cost the most money are rarely the ones that throw an error message. Nobody notices these until a customer mentions it weeks later, if they mention it at all.

  • Form notification emails landing in spam. The form technically submits. The lead never reaches an inbox anyone actually checks.
  • A redirect that quietly points to the wrong page. Traffic keeps arriving, conversions keep dropping, and nothing in the dashboard flags it as broken.
  • Tracking code that stopped firing after a plugin update. The ads keep running. The reporting keeps looking normal. The numbers are just wrong.
  • A third-party script slowing every page down by a second or two. Nothing crashes. Visitors just quietly leave before the page finishes loading, and there’s no log entry for someone who got impatient and closed the tab.

None of these throw an error. They just cost money in a way that never shows up unless someone goes looking on purpose.

Why “it works” is such an easy trap

Checking whether a site works takes thirty seconds. Checking whether it’s actually done, actually fast, actually converting at the rate it should, takes real time and a level of attention most owners are too busy running the business to give it. So “it works” becomes the finish line by default, not because anyone decided it should be, but because nobody budgeted the time for the harder question.

A redesign, on the other hand, feels productive in a way that testing a form never will. New colors, a new layout, a fresh homepage: it looks like progress in a screenshot. Fixing a silent email delivery failure looks like nothing at all, even when it’s worth more to the business than any redesign would be.

Where to actually spend your time

  1. Test what converts. Is the form working. Is the phone number tappable. Do leads actually arrive.
  2. Fix what’s broken. Broken links, failed form deliveries, slow load times.
  3. Remove what’s unnecessary. Every plugin you’re not actively using is a security risk and a speed cost.
  4. Then, and only then, consider visual changes.

Notice the order. Testing comes before fixing, and fixing comes before removing, and removing comes well before anyone touches a color palette. Most owners run that list backwards, starting with the redesign because it’s the fun part and ending with the form testing never, because nobody enjoys it.

A lot of what a stack of small plugins is trying to do, send a follow-up email, log a lead somewhere, ping your phone, is a rounding error’s worth of code once someone sits down and writes it properly. That’s the kind of cleanup real business automation work looks like, not another plugin stacked on top of the last one.

Plugins that are usually safe to replace with something simpler

  • A popup plugin running on every page just to show one announcement bar.
  • An image compression plugin doing cleanup work on every upload when the images were never resized to the right dimensions to begin with.
  • A related-posts plugin querying the database on every single page load for a feature almost nobody clicks.
  • A social share plugin loading several separate tracking scripts just to display four icons.

None of these are bad plugins on their own. The problem is stacking four or five of them onto a small site that only needed one small piece of code doing one small job, and then never revisiting that decision once the immediate need passed. Each one sitting there unused is still getting scanned by bots, still needing security updates, and still slowing down every page load for a feature nobody’s using anymore.

A quick audit you can run this week

  1. Submit your own contact form right now and time how long the confirmation email takes to arrive.
  2. Open your plugin list and write down what each one actually does. If you can’t answer in one sentence, that’s a candidate for removal.
  3. Check your homepage load time on a phone, not just a desktop monitor sitting on fast office internet.
  4. Open your logo file’s actual dimensions and compare them to the size it displays at on the page.

None of these steps take more than a few minutes. Together they’ll tell you more about what your site actually needs than a redesign brief would.

What to do with what you find

If the form is slow or silent, that gets fixed today, not scheduled for next quarter. If a plugin’s job is unclear, deactivate it and watch for a week before deleting it outright. If the logo is oversized, replace it with a properly sized file, which usually takes less time than it took to notice the problem in the first place. None of this is glamorous work. It’s also the work that actually protects revenue, which redesigns rarely do on their own.

Leave the tinkering for the garage

A website that works and converts is done until the data says otherwise. Redesigning for the sake of redesigning is expensive comfort, not progress.

Save the tinkering instinct for something that’s supposed to never be finished. Your website has a job to do. Once it’s doing that job well, the best thing you can do most weeks is leave it alone and go find the next actual problem instead of inventing one.

Frequently asked questions

How do I know if my website actually needs a redesign?

Check the fundamentals first: does the contact form work, is the site fast on a phone, and are leads actually arriving. If those are solid, a redesign is usually a want, not a need. If those are broken, fix them before spending money on how the site looks.

How many plugins is too many for a small business site?

There’s no fixed number, but if you can’t say in one sentence what a plugin does or when it was last useful, it’s a candidate for removal. Each unused plugin is ongoing security risk and load time with nothing to show for it.

What should I test on my website regularly?

At minimum, submit your own contact form and confirm the notification arrives, check that your phone number is clickable on mobile, and check page load speed on a phone. These take a few minutes and catch most of the problems that quietly cost leads.