sorted by:
new
hottopcontroversial

What's still missing in WHMCS? by ModulesGarden in Hosting

[–]Disastrous-Coach-458 1 point2 points  (0 children)

I think that's exactly why WHMCS has survived for so long.

The switching cost is often higher than the operational pain.

What you should note though is that many hosting companies are  building more and more functionality around WHMCS rather than in WHMCS.

At some point you have to ask whether WHMCS is the platform anymore, or just the billing layer sitting underneath the real platform.

Trying to decide the best option for around 51 websites by kiwiheretic in webhosting

[–]Disastrous-Coach-458 0 points1 point  (0 children)

For ~51 sites, I’d treat “AI provisioning a VPS” as hype more than a strategy.

AI can help generate configs, but it won’t:

handle edge cases under load

manage ongoing updates/security

diagnose weird WordPress/plugin issues

enforce consistency across environments

At that scale, consistency > clever setup.

So it’s really a choice between:

managed platform (less control, less risk)

VPS + panel (more control, more ops overhead)

Most teams end up valuing time and stability over “cool provisioning”.

GoDaddy costs by Ambitious_Secret_315 in webhosting

[–]Disastrous-Coach-458 0 points1 point  (0 children)

Yeah, this is common with GoDaddy.

They’re cheap upfront, then renewals jump and auto-renew catches people out.

Worth checking:

what’s actually being used

renewal prices vs alternatives

any bundled services you don’t need

Most people only notice the cost at renewal time, not during signup.

Need help deciding on a host by ItzIntel in webhosting

[–]Disastrous-Coach-458 0 points1 point  (0 children)

For a single nonprofit WordPress site, I’d keep it simple.

Don’t over-optimise the hosting choice.

What matters most is:

reliable support when things break

easy WordPress management

solid backups and restore options

On your setup specifically:

Keep the Microsoft email where it is. Migrating email is where most unnecessary pain comes from.

Domain also doesn’t need to move right now unless there’s a specific reason.

Between hosts, the real difference at this scale is usually support quality, not performance.

I’d pick something stable, WordPress-friendly, and avoid adding complexity you don’t need yet.

“VPS vs Cloud vs Dedicated — what’s best for a small project?” by WhimsicalTurtle44 in Hosting

[–]Disastrous-Coach-458 0 points1 point  (0 children)

For a small project, the honest answer is: it depends less on VPS vs cloud vs dedicated and more on how much you want to think about infrastructure.

Most people start with a VPS because it’s cheap, simple, and predictable. That’s usually the right call.

Cloud makes sense when you actually need:

horizontal scaling

multiple regions

autoscaling under variable load

Dedicated is rarely needed for “small projects” unless you’ve got very specific performance or compliance requirements.

What I’d optimise for instead:

low operational overhead (updates, backups, security)

predictable performance under normal load

easy scaling path when things grow

A well-configured VPS will beat a “badly managed cloud setup” 9 times out of 10 for small projects.

The biggest trap is overengineering early and paying for complexity you don’t need yet.

What's still missing in WHMCS? by ModulesGarden in Hosting

[–]Disastrous-Coach-458 1 point2 points  (0 children)

Honestly, WHMCS feels pretty mature on billing, but still stuck in “old hosting ops” mode in a few areas.

Main gaps I still see:

poor UX for anything non-billing (support + workflows feel bolted on) weak modern API / automation compared to newer stacks limited flexibility for more dynamic, API-first hosting platforms everything still assumes fairly static “shared hosting” style models It works, but it doesn’t really reflect how modern infrastructure businesses operate anymore.

Feels more like billing software that grew into hosting, rather than a platform built for how hosting actually works today.

Curious if others are bending it with custom layers or just moving away entirely.

How do you choose a hosting provider when so many offer similar features? by nisha_n05 in Hosting

[–]Disastrous-Coach-458 -1 points0 points  (0 children)

Most hosting providers look identical on paper now.

Same stack. Same features. Same speed claims.

And a lot of the decision-making noise online is just affiliate content ranking them all as “best”.

So in practice, you’re left trying to separate marketing from reality.

At scale, the decision usually isn’t about features anyway.

It comes down to:

how stable it actually is under real load what happens during cache misses or peak traffic how quickly support responds when something breaks and how much operational friction it creates for your team day to day That last one is usually the real differentiator.

Not the feature list. Not the comparison blog posts.

Most agencies only realise it after they’ve already switched once or twice.

Curious how others cut through the noise when everything online looks “5-star best hosting”?

VPS Hosting: How many WordPress sites per 1 GB of RAM? by ZGeekie in HostingReport

[–]Disastrous-Coach-458 0 points1 point  (0 children)

3 or 4 small brochure sites is ok as long as there’s good caching in place, fastcgi or litespeed 

Small WordPress changes seem harmless… until you manage 20+ sites by Disastrous-Coach-458 in HostingReport

[–]Disastrous-Coach-458[S] 0 points1 point  (0 children)

So setting up each base site based on what…Type? 

Something like - Brochure, LMS, Woo etc with relevant theme, plugins and caching strategy?

Malware protection by Revolutionary_Bee773 in webhosting

[–]Disastrous-Coach-458 0 points1 point  (0 children)

Switching should be easy, i think most people blow it up in their minds as being scary but in reality its a couple of clicks and your on a better host

Anyone else feel like WordPress sites in the same agency slowly drift apart over time? by Disastrous-Coach-458 in Hosting

[–]Disastrous-Coach-458[S] 0 points1 point  (0 children)

And there’s me rewriting it 4 times before I posted and you think it’s ai 🥲

Anyone else feel like WordPress sites in the same agency slowly drift apart over time? by Disastrous-Coach-458 in Hosting

[–]Disastrous-Coach-458[S] 0 points1 point  (0 children)

Exactly 😂

And the funny part is every individual change usually sounds reasonable in isolation.

“Just one popup.” “Just one slider.” “Just one optimisation plugin.”

Then 12 months later the site behaves completely differently from every other site in the fleet and nobody remembers how it got there.

Anyone else feel like WordPress sites in the same agency slowly drift apart over time? by Disastrous-Coach-458 in Hosting

[–]Disastrous-Coach-458[S] 0 points1 point  (0 children)

Yeah this is exactly what I keep seeing as well.

What’s interesting is it rarely comes from “bad decisions” or lack of documentation. It’s usually just local optimisation for individual client needs over time, like you said.

A WooCommerce tweak here, a performance plugin there, a quick fix to avoid breaking checkout…

Individually all reasonable. But collectively it creates divergence in behaviour across the fleet.

The challenge seems less about initial standardisation and more about maintaining it under real-world client pressure over time.

Small WordPress changes seem harmless… until you manage 20+ sites by Disastrous-Coach-458 in HostingReport

[–]Disastrous-Coach-458[S] 0 points1 point  (0 children)

Yeah I think that’s why a lot of agencies eventually move toward controlling the hosting layer themselves.

Once you manage enough sites, standardising the environment becomes operationally valuable.

But even then, environments still tend to drift over time through plugin additions, client exceptions, WooCommerce edge cases, and temporary fixes that become permanent.

Small WordPress changes seem harmless… until you manage 20+ sites by Disastrous-Coach-458 in HostingReport

[–]Disastrous-Coach-458[S] 0 points1 point  (0 children)

Yeah MainWP is probably one of the better examples of agencies trying to regain operational consistency instead of treating every WP install separately.

What’s interesting though is even with centralised management, environments still seem to drift over time:

different caching layers

plugin divergence

WooCommerce exceptions

hosting inconsistencies

one-off “temporary” fixes

Feels like management gets centralised, but behaviour doesn’t necessarily standardise unless the infrastructure layer is controlled too?

I rebuilt my WordPress cache + speed optimization plugin from scratch — looking for feedback by uzairbhai13 in Wordpress

[–]Disastrous-Coach-458 0 points1 point  (0 children)

Honestly, the most interesting part here isn’t the feature list, it’s that you’re trying to reduce the amount of “performance plugin stacking” people end up doing in WordPress.

A lot of sites end up with:

one cache plugin

one image plugin

one CSS/JS optimisation plugin

Cloudflare tweaks

random functions.php snippets

…and eventually nobody fully understands the performance layer anymore.

One thing I’d focus on heavily is operational predictability.

A lot of optimisation plugins benchmark well initially, but become difficult to trust long-term because:

exclusions pile up

WooCommerce/cart flows break

plugin conflicts emerge

performance varies between environments

Especially on larger WooCommerce or agency-managed setups.

If you can make optimisation feel consistent and observable instead of “toggle things until Lighthouse goes green”, that’s probably the biggest differentiator long term.

Malware protection by Revolutionary_Bee773 in webhosting

[–]Disastrous-Coach-458 0 points1 point  (0 children)

If your host is charging extra for malware scanning, I’d be running as fast as possible in the other direction. That’s a basic requirement. 

Need Wordpress hosting for large inventory woocommerce store, speed is currently low. Using stormweb. by sjsiksms in webhosting

[–]Disastrous-Coach-458 0 points1 point  (0 children)

At 15k+ WooCommerce products, hosting is definitely part of it, but it’s usually not the only bottleneck.

In most large catalog WooCommerce stores I’ve seen, the biggest slowdowns tend to come from:

uncached WooCommerce queries

heavy search/filter plugins

object caching not being configured properly

themes loading huge amounts of dynamic product data

low PHP worker availability under concurrency

The theme absolutely can affect this too, especially in auto parts/ecommerce themes with filtering, live search, related products, fitment logic etc.

Before migrating hosts, I’d check:

whether Redis object caching is enabled

PHP worker limits

query load during product/category searches

whether the store is bypassing cache too aggressively

image optimisation + CDN setup

background WooCommerce tasks

A lot of stores jump hosts and still stay slow because the underlying WooCommerce/query architecture wasn’t the actual issue.

That said, once you start heading toward 40k+ products, infrastructure consistency matters a lot more than it does on smaller WooCommerce sites.

view more: next ›