Why a Good Website Needs More Than Good Design

A beautiful website is only the beginning

I came to web development through design and photography, so I'll be the last person to say looks don't matter. They do.

My own web work began before content management systems became commonplace, building websites by hand with HTML, CSS, JavaScript and Flash, and I also gained experience as a webmaster.

Good visual design creates a first impression. It helps establish credibility, communicate professionalism and make a business memorable.

But after years of designing, developing and maintaining websites, I've learned that appearance is only one part of the equation.

A website can look impressive and still be slow, difficult to update, expensive to maintain or poorly suited to the business it represents.

A good website should do more than look professional. It should work reliably, support the business and remain manageable long after launch.

That starts with decisions made before the first page is designed.

That includes choosing the right platform. WordPress remains a capable, flexible platform, and for many businesses it's exactly the right choice. As businesses grow, though, some need more: integrations with other systems, custom functionality, automation or more sophisticated digital systems. That's when a different approach can make sense. Neither option is automatically better; the right choice depends on what the business needs.

What years of working with WordPress taught me

I've worked extensively with WordPress over the years. It's a capable platform, and there's a reason so many businesses use it.

On WordPress projects, I've also worked with experienced developers, particularly for custom themes, specialised plugins, complex configurations and security troubleshooting. Sometimes that's a question of workload, but often the project needs specialist technical expertise, and bringing in the right person is part of doing the job well.

But I've also experienced the challenges that can arise when websites rely on numerous themes, plugins and third-party components.

A plugin update can conflict with another plugin. A theme that worked perfectly with an older version of PHP may develop problems after a server upgrade. A website that hasn't been maintained for months can become increasingly difficult to update without something breaking.

Performance can also suffer.

Many multipurpose themes come with features designed to accommodate different kinds of websites. That's convenient during development, but it can mean loading CSS, JavaScript and other resources that a particular website—or even a particular page—doesn't need.

Add several plugins, each introducing its own scripts and styles, and a relatively simple website can become unnecessarily heavy.

Of course, these problems aren't inevitable. A carefully built and maintained WordPress website can perform very well.

The difficulties I've encountered have often come from accumulated complexity and a lack of ongoing maintenance.

When maintenance becomes an emergency

One particularly difficult aspect of website maintenance is convincing clients that it matters before something goes wrong.

I've worked with some clients who were reluctant to invest in regular maintenance. Over time, their WordPress installations, themes, plugins or server environments became outdated.

In some cases, websites were eventually compromised by malware.

I've personally dealt with these situations. Where clients had subscriptions, I used Sucuri to help clean infected websites. In other cases, I worked with an experienced developer to identify and remove malicious files manually.

But manual cleanup isn't always straightforward.

Malicious code can be hidden in unexpected locations, and removing the obvious infection doesn't necessarily mean everything has been eliminated. Without proper investigation and recovery procedures, a website may remain vulnerable to reinfection.

Those experiences reinforced an important lesson:

Preventing problems is generally better than repeatedly repairing them.

Security, maintenance and recovery should be considered part of website development—not optional extras introduced after an incident.

The solution starts before development

When someone approaches a developer about a new website, the conversation often begins with appearance.

What colours should we use? What should the homepage look like? Can we make it similar to another website?

Those are reasonable questions, but I believe more important questions should come first.

What does the business need the website to accomplish?

Who will use it? Who will maintain it? What information changes regularly? Will it eventually need integrations, booking functionality, customer accounts or an internal dashboard?

A website built primarily around its initial appearance may require considerable changes when the business discovers what it actually needs.

I prefer to understand those requirements early.

That doesn't mean predicting every feature a business might want in five years. It means making sensible architectural decisions today so that tomorrow's changes don't automatically require rebuilding everything.

It also means choosing technology based on the project rather than choosing a platform first and forcing every requirement into it.

When a custom-built website makes sense

My experience maintaining traditional websites has influenced how I approach development today.

I increasingly work with technologies such as Next.js, React, TypeScript, Sanity and Vercel to create websites and digital systems tailored to particular business requirements.

Alongside websites, that work includes structured content management, business dashboards and data integration, automation and customised workflows, staging environments with controlled publishing, and internal web applications and business systems. I'm currently working on a restaurant website for a client in New Zealand.

One of the biggest advantages is control over what gets built.

Instead of starting with a multipurpose theme and adding plugins until the required functionality is available, I can design the structure around what the business actually needs.

That creates opportunities to reduce unnecessary components, avoid certain plugin dependencies and make the overall system easier to understand.

A different approach to maintenance

This is an important distinction.

A custom-built website doesn't require the same kind of routine theme-and-plugin maintenance as a WordPress website that relies heavily on third-party extensions.

There may be fewer unrelated components to update and fewer compatibility issues between plugins.

That can reduce a significant source of recurring maintenance work.

However, custom-built does not mean maintenance-free.

Frameworks and software dependencies still need security updates. Hosting and integrations need monitoring. Forms, authentication and other functionality need testing. Backups and recovery plans still matter.

Custom development also introduces responsibilities that don't necessarily exist with an established, well-supported off-the-shelf solution.

The benefit isn't that maintenance disappears. It's that a carefully planned system can have a more focused set of dependencies and a maintenance process better suited to its actual functionality.

For businesses, that distinction can be valuable over the long term.

Performance should be designed in, not added later

Speed affects how people experience a website.

A visitor shouldn't have to wait unnecessarily for the main content to appear, struggle with unresponsive controls or watch the page shift while images and fonts load.

Google's Core Web Vitals (opens in a new tab) provide useful measurements for loading performance, responsiveness and visual stability.

Research has also linked improved website speed with better business outcomes. A Deloitte study commissioned by Google (opens in a new tab), for example, examined how small improvements in mobile speed related to conversion rates in retail and travel.

As a photographer, I'm particularly conscious of image quality.

A website should showcase photographs beautifully, but uploading large original files without considering their delivery can create unnecessary delays.

Image dimensions, compression, modern formats and responsive delivery all matter.

But image optimisation is only part of the solution. Unnecessary scripts, fonts, plugins and other resources can affect performance just as much.

This is another reason I prefer to consider performance from the beginning rather than treating it as something to fix after launch.

A website should be easy for its owner to manage

One of the most overlooked aspects of website development is the experience of the people who will maintain its content.

Businesses change.

Services evolve, team members join or leave, photographs need replacing, and information becomes outdated.

If every small change requires a developer, the website can quickly become a burden.

A content management system should make routine updates straightforward without exposing users to unnecessary technical complexity.

This is one reason I work with structured content management systems.

One publicly available example is my work on dcInvest.global (opens in a new tab), which includes a Sanity-based content management system and a separate staging environment for checking changes before they reach the public website.

The objective is to separate routine content editing from the underlying website design and functionality.

A business should be able to manage its information without accidentally changing the structure of its website.

That principle matters regardless of which platform is used.

Accessibility is part of good design

Accessibility is sometimes treated as an additional technical requirement, but many accessibility decisions begin with design.

Text needs sufficient contrast. Navigation should work without a mouse. Images should have appropriate descriptions. Forms need clear labels and understandable feedback.

A beautiful interface that some visitors cannot use isn't a complete design solution.

The scale of the problem is significant. WebAIM's 2026 Million report (opens in a new tab) found automatically detectable accessibility failures on the overwhelming majority of the homepages it tested.

Automated testing doesn't identify every accessibility problem, so practical testing and thoughtful design remain important.

For me, accessibility is another reason to consider how a website works—not just how it appears in a presentation.

The hidden cost of choosing a website

Businesses naturally consider the initial development cost when commissioning a website.

But the initial price isn't the whole cost.

A website may also require hosting, maintenance, security monitoring, performance improvements, new functionality and occasional repairs.

A less expensive website can become costly if it repeatedly needs troubleshooting or extensive modifications.

Equally, a custom-built website isn't automatically the more economical option.

For a straightforward business website, a well-configured WordPress installation with a suitable theme and limited plugins may be entirely appropriate.

A more complex business may benefit from a custom architecture, particularly when the website needs structured content, integrations, specialised functionality or room to evolve into a larger digital system.

The right decision depends on requirements, budget and long-term responsibilities.

The objective should be to choose the most appropriate solution—not simply the cheapest or most technically impressive one.

The website should belong to the business

There's another issue I believe deserves attention: ownership.

Businesses should understand who controls their domain, hosting, content, source code and third-party services.

They should also know what happens if they eventually decide to work with another developer.

Good documentation, appropriate access and clear ownership arrangements make future changes easier.

I believe a professionally delivered website should help a business become more capable—not unnecessarily dependent on the person who built it.

Clear content matters as much as the technology

Even the fastest, most technically sophisticated website won't be effective if visitors cannot understand what the business offers.

People often scan web pages rather than read every word. Nielsen Norman Group's research (opens in a new tab) has long highlighted this behaviour.

Visitors should quickly understand what the business does, who its services are for and what they should do next.

That might mean requesting a quotation, making an enquiry, viewing previous work or arranging a consultation.

The design, content and technology should support that journey together.

A website shouldn't make visitors work hard to understand the business.

What to consider before commissioning a website

Before beginning a new website project, I'd encourage business owners to ask a few practical questions:

• What business objectives should the website support?
• Why is a particular platform or technology being recommended?
• Would a template-based website be sufficient, or is custom development justified?
• Can the team update important content without technical assistance?
• How will performance, accessibility and mobile usability be tested?
• Who will manage security, software updates and backups?
• What ongoing costs should the business expect?
• Can the website accommodate future integrations or additional functionality?
• Who owns the website's content, accounts and source code, and how would a future handover work?

These questions are easier—and usually less expensive—to address before development than after the website has been completed.

A good website should continue working for the business

After years of working across photography, visual design, website development and maintenance, I've learned that some of the most important decisions happen before the first page is built.

Choosing the right technology, understanding how the business operates, planning for performance and security, and making content easy to manage are just as important as the visual design.

My years with hand-coded websites and WordPress taught me the consequences of unnecessary complexity and neglected maintenance, problems that can affect any platform. My more recent work with custom-built websites has given me additional ways to address those challenges from the beginning.

Neither approach eliminates the need for good planning or responsible maintenance.

But choosing the right approach early can make a meaningful difference to how a website performs, how easily it evolves and how much effort it requires to keep running.

A good website should look professional on launch day. A well-planned website should continue working for the business long after that.

If you're planning a new website or reconsidering an existing one, I'm happy to discuss what approach would make sense for your requirements. Get in touch.