This morning, a customer’s website went offline. For them it meant a blank page, lost enquiries, and lost revenue. For us it was a technical problem to solve - FAST!!! Here’s the process we followed:
- Log in to the server: direct access to the hosting environment, not just a control panel.
- Check the error logs: identify whether the failure was caused by code, traffic load, or server resources.
- Restart PHP-FPM: the service that handles website processes. Restarting it cleared blocked workers.
- Adjust worker levels: tuning how many processes could run at once to prevent the issue recurring.
- Test and confirm: check the site from multiple locations, confirm speed, and monitor stability.
The whole process took minutes. The client’s business was back online before most visitors noticed. But the key question is this: without someone technically competent to call, what would have happened? On a DIY builder or a cheap template site, there’s no access to logs, no ability to restart services, and no control over resource allocation. You wait in a help-desk queue while your site — and your business — stays offline.
What This Shows
A website doesn’t fail in the same way a light bulb does. When a site goes down, the cause can be hidden layers deep in the stack — server processes, database queries, or resource limits. Here’s what the morning incident revealed in technical terms:
- Server access: fixing the issue required logging into the hosting environment directly, not just a control panel. Without this access, you simply can’t see what’s happening under the hood.
- Error logs: the first step was checking log files. These revealed that PHP workers were blocked. On a DIY platform, those logs are invisible. All you see is “site unavailable.”
- PHP-FPM processes: modern WordPress and WooCommerce sites rely on PHP-FPM to handle requests. Restarting the service cleared the blocked workers. This kind of restart isn’t available on shared DIY hosting.
- Worker level tuning: we increased the number of PHP-FPM workers to handle current demand. This is performance engineering — balancing memory use against concurrency so that future spikes don’t crash the site.
- Validation: finally, testing from multiple endpoints ensured the fix held and that load times stayed consistent.
From a business perspective, the key difference is this: a DIY or template-built site might look fine on the surface, but when the underlying system fails, there’s no way to diagnose or resolve it quickly. Professional builds come with the technical access and the expertise to act within minutes, not hours or days.
DIY or Builder Websites (e.g. Wix, Squarespace, Shopify Starter)
Cost: around $500–$1,000 per year including hosting, domain, and the builder subscription.
DIY builders are the fastest and cheapest way to get online. For a small service business or a start-up, that can be the right choice. You choose a template, add your logo and details, and you have a website within days. These platforms also include basic hosting, SSL security, and simple support. For businesses testing an idea, that’s often enough.
It’s also fair to say that some DIY platforms have evolved into serious tools. Wix Studio, for example, now powers large-scale corporate sites with robust business features. Squarespace and Shopify have similar enterprise offerings. In other words, it’s not that these platforms can’t scale — it’s that most small businesses never need or use that capability.
The real issue is not the platform itself, but what happens when something breaks. This morning’s outage was resolved in under 20 minutes because we had direct server access, log files, and the ability to restart and tune PHP-FPM. On a DIY system, those layers are hidden. If the site fails, you wait in a help-desk queue, often without a clear answer, while your business stays offline.
This is where local support makes a difference. Having technically competent people you can actually call — who know your business and your site — is priceless. Instead of waiting on a ticket number, you get a direct response and a fix, often before customers even notice there was a problem. Supporting a local company also means you’re not one of thousands in a global queue, but a client with a name and a relationship.
So, a DIY or builder site is a valid starting point, and in some cases a long-term solution. But the trade-off is control. Whatever platform you use, you still need technically competent people to keep things running smoothly — and that’s the gap many small operators discover too late.
When Customisation Matters
A simple DIY or template site is fine for showing services and contact details. But what if your business model relies on more than static pages? This is where customisation makes the difference between a website and a platform.
Take onw= example of a website we built for members. It’s not just a brochure — it runs a monthly random draw for members, manages different membership tiers, integrates an email system, and delivers video content through a content delivery network (CDN) to keep performance high. These are requirements that go far beyond what a DIY template can deliver out of the box.
- Membership logic: tiered plans, recurring payments, and accumulated draw entries.
- Random draw system: automated, transparent, and fair — built as custom code.
- Email integration: synchronised with member actions so communication is timely and personalised.
- Video performance: hosting on a CDN ensures smooth playback without overloading the main site.
For businesses like this, the website is not just a presence — it’s the operating core. Achieving that requires a blend of theme builders for flexibility, custom code for business logic, and engineering practices to make it all reliable under load.
The Trade-Off: Customisation
A basic DIY or template site is fine for showing services and contact details. But what if your business model depends on features that go far beyond static pages? This is where customisation becomes the deciding factor — and where the costs can quickly change.
Take the example of CruiseLife.com.au. This site runs a monthly random draw, manages multiple membership tiers, integrates with an email system, and delivers video content through a content delivery network (CDN) to keep performance smooth. None of this comes “off the shelf.” It requires a carefully engineered build.
Could a DIY platform like Wix or Squarespace do this? In theory, yes. With enough third-party apps or by hiring developers inside their ecosystem, you could stitch the pieces together. But that’s no longer a $500 site. Customisation of this kind can easily cost $10,000–$20,000+ and you remain locked into the platform’s limits, dependent on their app store, their hosting, and their support queues.
By contrast, an open framework such as WordPress and WooCommerce makes this type of customisation possible — for a competent developer. Out of the box, it’s no simpler than any other system. But in the right hands it offers full control: membership logic, random draws, email automation, and video delivery can all be integrated directly with custom code and engineered infrastructure. The result is more flexible, more transparent, and far more cost-effective over time.
The trade-off is not really “DIY vs professional.” It’s about how far you need to go. For a dog wash or café, a simple DIY page may be perfect. For a membership platform or a business with custom workflows, professional engineering saves both money and risk in the long run.
Integration and Peace of Mind
For many businesses, the website is just one part of the operation. Products need to sync with supplier feeds, stock levels must match the point-of-sale (POS) system in store, and online orders need to flow smoothly into accounts or inventory. Without proper integration, staff are stuck reconciling spreadsheets and customers see out-of-date stock or prices.
A competent developer can integrate WooCommerce with product feeds, supplier APIs, and POS systems at a fair price. Done properly, this means:
- Product feeds: prices and availability update automatically from suppliers, keeping the store accurate without manual uploads.
- POS integration: in-store and online stock stay in sync, so customers don’t buy what isn’t there.
- Email and CRM links: orders and customer data flow directly into the right systems for follow-up and marketing.
But the work doesn’t end at launch. APIs change, feeds can fail, and POS software updates can break connections. The real value is having ongoing technical support that monitors these links and fixes issues before they become business problems. That peace of mind — knowing someone is watching the system while you run the business — is what keeps the whole operation stable.
What’s Under the Hood
From the outside, two websites can look almost identical. Both may have sharp images, neat layouts, and a modern style. But the difference lies under the hood — in the technical build that determines speed, stability, and long-term reliability.
- Load time optimisation: compressing and resizing images properly, minimising scripts, and using caching so pages load in fractions of a second.
- Content delivery networks (CDNs): placing videos, images, or even the whole site on global servers so customers load content from the nearest location, not the other side of the world.
- Server tuning: adjusting PHP-FPM worker levels, memory allocation, and process limits so the site can handle heavy traffic without failing.
- Database engineering: WooCommerce depends heavily on its database. Without proper indexing, query optimisation, and housekeeping, product searches slow down, carts stall, and admin tasks grind to a halt. With the right tuning, those same tasks can run cleanly in minutes — or even seconds.
- Security and resilience: hardened server settings, SSL configuration, and regular backups so the business isn’t exposed when something goes wrong.
A real example makes the point. Recently, large product synchronisation jobs were taking 35 to 110 minutes to complete, dragging down performance and retrying thousands of times. After database optimisation and query tuning, the same jobs now run in under two minutes — some in just a few seconds — with no impact on the live site. That’s the difference between “looking good” and being engineered to run a business.
Choosing the Right Path
Every business needs a website, but not every business needs the same kind of website. For some, a simple DIY page or cheap template is enough to get started. For others, the website is the business — and downtime, slow performance, or broken integrations cost money every day.
The decision isn’t really “DIY vs professional.” It’s about matching the site to your stage:
- Testing the waters: a DIY site can be a smart, low-cost way to get online quickly.
- Growing a local service: a template build may give you a neat brochure site, but without much technical depth.
- Relying on your site for sales: you need professional engineering — fast load times, stable hosting, secure data, and someone to call when things go wrong.
- Running complex systems: product feeds, POS integration, membership logic, or video delivery all demand a properly engineered platform with ongoing support.
That’s the trade-off. Any site can look attractive on launch day. The difference comes six months later — when traffic grows, stock feeds need syncing, or the server fails at a busy hour. At that point, the value of competent, local technical support is obvious.
At Sydney Business Web, our focus is building sites with those foundations from day one. A standard 10-page site with SSL, privacy compliance, hosting, and a year of real technical support typically costs around $2,500 — engineered to perform, scale, and give business owners peace of mind. In other words, not just a website, but an asset you can rely on.
