An Honest Answer From Someone Who Sells It

Every article answering this question is written by a maintenance company, and every one of them concludes: yes, everyone, always, urgently. That’s not analysis, that’s a sales page wearing a hat.

So here’s the version we’d tell a friend: some sites genuinely don’t need a paid maintenance plan, and paying for one anyway is wasted money. Others need one far more than their owners realize, and the gap between the two comes down to a handful of questions you can answer in five minutes.

The three questions that actually decide it

1. What does a day of downtime cost you, in money and in trust?
If the honest answer is “nothing, really” a personal blog, a hobby project, a placeholder site, then the economics of paying $100+/month for protection don’t close. If the answer involves lost inquiries, lost orders, or a first impression ruined for a customer who was checking you out before calling, the economics close fast. A single lost client usually costs more than a year of maintenance.

2. Who notices when something breaks? You, or your visitors?
This is the sneaky one. Sites don’t announce their failures. Contact forms stop delivering silently. Checkout errors happen to customers, not to owners. A hacked site often looks perfectly normal to you while showing spam to Google. Without monitoring, the detection system is “an annoyed customer mentions it”, and for every one who mentions it, more just left. If your site has a job, someone needs to be watching whether it’s doing that job.

3. Is anyone actually doing the work now?
Most business sites exist in a specific limbo: the owner believes the “website person” handles things; the website person finished the project two years ago and handles nothing. Updates pile up (check your own admin, the little orange circles are counting), backups are whatever the host does, and nobody has tested a form since launch. The question isn’t “maintenance: yes or no” — maintenance is happening or it isn’t, and “it isn’t” is a decision too, just an unmade one.

The honest decision table

Your situation	Honest recommendation
Hobby/personal site, downtime costs you nothing	No paid plan. Turn on auto-updates, use a free backup plugin to cloud storage, accept the small risk of an occasional breakage. This is fine.
You’re technical and actually enjoy the upkeep	DIY with the full checklist: staging tests, off-site backups you restore-test, monitoring. The plan-vs-DIY question is about time, not capability.
Business site, generates inquiries or sales, nobody technical is actively responsible	This is who maintenance plans exist for. Not because disaster is certain but because silent degradation is.
Revenue-critical site or WooCommerce shop	Beyond “should”: the real question is response time and whether checkout is tested after every update. Downtime here is measured in money per hour.
Agency with a portfolio of client sites	Different problem (scale + your reputation on every site). We wrote about the white-label model separately.

“But my site has been fine for three years without any of this”

The most reasonable objection, and it deserves a straight answer: yes, that happens. Sites survive on luck for years, genuinely, not sarcastically. The catch is that this argument works right up until the day it doesn’t, and the failure it doesn’t work against isn’t evenly distributed: it’s the outdated-plugin compromise, the update conflict, the never-tested backup, all of which accumulate probability over time rather than resetting each year. Unmaintained isn’t “proven safe”; it’s “not yet unlucky.” What you’re buying with maintenance isn’t the prevention of a certainty, it’s the conversion of a small chance of a very expensive week into a known, boring monthly cost. That’s insurance logic, and like all insurance, whether it’s worth it depends on question 1 above, not on how lucky you’ve been so far.

What you should get if you do pay

If your answers point toward a plan, ours or anyone’s, the checklist of what “real” looks like, so you can compare providers on substance:

Updates tested on a staging copy before your live site is touched
Off-site backups with retention, restore-tested, not “the host does backups”
Security scanning plus a firewall, with a human reviewing results
Forms and key functions tested on a schedule, the silent-failure detector
A monthly report in plain language — the proof that any of this happened
No lock-in: you keep hosting, credentials, and backups; leaving is easy

Anything sold cheaper than ~$75/month is almost certainly missing the staging and the human review, which are the two items doing most of the protecting.

The five-minute way to decide with data instead of vibes

You don’t have to answer the three questions by feel. Our free Health Check audits your site across seven areas and effectively answers question 3 for you: what state the site is actually in, what’s being neglected, and what, if anything, genuinely needs ongoing attention. If the report comes back clean and your downtime cost is low, we will happily tell you that you don’t need us. That’s not a marketing line; a client who didn’t need a plan and bought one anyway becomes a cancellation with a bad taste in six months. Honest triage is the better business.

Request the free Health Check →

The Five Real Causes, in Order

Let’s clear the air first: WordPress is not slow. This site runs on WordPress, on ordinary shared hosting, and scores 100/100 on Google’s PageSpeed test on mobile, the hard one. No exotic infrastructure, no tricks. WordPress setups are slow, and they’re slow in remarkably predictable ways.

If your site takes four, six, eight seconds to appear, the cause is almost certainly on this list. In fix-this-first order:

1. Page weight: you’re shipping too much

The most common cause is the simplest: the page is huge. A 6 MB photo dropped straight from a phone into the hero. Five font families. A video that autoplays. Sliders. The browser can’t paint what it hasn’t downloaded, and on mobile connections, megabytes are seconds.

The fixes are unglamorous: images resized to the size they display at, compressed, served as WebP; fonts trimmed to the two or three weights actually used; the slider replaced with one strong image (sliders hurt conversions anyway, that’s a separate article’s worth of data). Weight is also the fix with the best effort-to-result ratio: it’s often possible to remove half a page’s bytes in an afternoon without changing how it looks.

2. Plugin bloat: forty little taxes on every visit

Every active plugin can add its own CSS and JavaScript to every page, run its own database queries, hook into every request. One plugin is nothing. Thirty-five plugins, the realistic average we find on sites that come to us, is a tax collected on every single page view. Worse, many load their assets everywhere: the contact-form plugin’s scripts on pages with no form, the shop scripts on the blog.

The fix is an audit, not a purge for its own sake: what does each plugin do, is it still needed, does a lighter alternative exist, and can its assets be restricted to the pages that use them? A recent rebuild took a client site from 23 plugins to 15, and load time from 4.2 s to 1.1 s.

3. No caching: WordPress rebuilds every page for every visitor

By default, WordPress assembles every page from scratch on every visit: PHP runs, the database answers a dozen queries, the HTML is generated. For the ten-thousandth identical view of the same homepage. Page caching stores the finished HTML and serves it instantly to the next visitor. It’s the single biggest server-side speedup available, it’s often a free plugin, and a shocking number of slow sites simply don’t have it turned on (or have it installed but misconfigured, which can be worse than nothing).

If your site is on cheap shared hosting, this is doubly important: caching is how a $10/month server behaves like a $100/month one.

4. Hosting that was never going to be fast

Sometimes the server is genuinely the bottleneck: ancient PHP versions (each major PHP release is meaningfully faster than the last), overloaded shared machines, no server-level caching, databases on spinning disks somewhere far from your visitors. The tell: even a stripped-down page with caching takes over a second to start responding (that’s TTFB — time to first byte).

Honest advice: don’t start here, even though every hosting company’s marketing says to. Weight, plugins, and caching usually deliver more than a hosting upgrade, and a bloated site moved to premium hosting is a bloated site with better scenery. Fix the site first; then judge the hosting on the clean result.

5. Theme and page-builder overhead

Heavyweight multipurpose themes and page builders generate deeply nested markup, load framework CSS/JS for features you don’t use, and add render-blocking assets, a structural tax on every page. This is the hardest cause to fix, because the theme is the site. Realistic paths: aggressive optimization within the builder, or when the business case supports it, a rebuild on a lean custom theme. This site is a custom theme for exactly that reason. Vortano custom theme weighs less than 300 KB, roughly a tenth of what Astra ships, and about 1–2% of a typical page-builder theme.

What mostly doesn’t help (despite the hype)

“Optimization” plugins stacked on a heavy site — minifying 4 MB of assets produces 3.7 MB of assets. Removal beats compression.
CDNs as a first move — a CDN distributes your site globally; it doesn’t make a heavy site light. Great later, not first.
Obsessing over a 100 score — Google’s own guidance is thresholds, not perfection: pass Core Web Vitals and spend the remaining energy on content. The difference between 92 and 100 is bragging rights (we enjoy them, but honestly: bragging rights). The difference between 45 and 85 is customers.

Why speed is a business number, not a vanity number

Google uses page experience in ranking, but the bigger effect is human: slow pages lose visitors before they load, and every additional second measurably increases the percentage who give up. For a site whose job is generating inquiries or sales, speed is conversion-rate infrastructure. That’s also why speed isn’t a one-time project — sites regain weight as content, plugins and updates accumulate, which is why performance monitoring is part of every care plan we run.

Find out which of the five is yours

Run your site through PageSpeed Insights — free, no signup — and look at the opportunities list, not just the score. Or let us do the reading for you: the free Health Check covers performance as one of its seven scored areas, names your specific causes in plain English, and tells you what fixing them would take.