WordPress sites that stay fast after you start editing them

What wordpress development actually means

WordPress website development here means a business website built on WordPress deliberately — because someone at your end will publish and edit — rather than by default. The build stays lean: a small number of load-bearing plugins, a theme that is not carrying features you will never use, and a structure that can grow without a developer.

WordPress is the right answer when content is part of your acquisition plan. It is the wrong answer when nobody will ever log in, and in that case a static build is faster, cheaper to host, and cannot be broken by an update at 2am.

Who this is for

• Trades and service businesses that need to be found locally and contacted quickly
• Teams who will genuinely publish — offers, updates, coverage areas, case studies
• Businesses replacing a site nobody can edit without paying someone
• Anyone whose current WordPress install has become slow, plugin-heavy or fragile
• Companies who need a site their marketing person can run without a ticket

Who it is not for

Saying this out loud costs me some enquiries and saves both of us the ones that would have gone wrong. If you are on this list, I will tell you in the first reply rather than after a deposit.

• Sites where nobody will ever log in. A static build serves you better and costs less to run
• Applications with real business logic in them — that is custom development, not a page builder
• Stores with unconventional catalogues, where WooCommerce will fight you
• Anyone unwilling to keep up with updates, because an unpatched WordPress is a breach waiting to happen

The problems it solves

A site nobody can edit

Pages structured so editing is safe, plus written instructions for the changes you will actually make.

Thirty plugins, four of them load-bearing

Plugin count kept in single figures, each one documented with what it is for.

Slow on a phone

Lean theme, image discipline, caching configured once and verified rather than assumed.

Enquiries that never arrive

Forms submitting server-side with authenticated email, so submissions are not lost to a spam folder.

Invisible in local search

LocalBusiness markup, consistent name/address/phone, and coverage content that is written rather than generated per town.

What you get

• Custom theme build — no bloated multi-purpose page builder
• WooCommerce configuration where you sell online
• Core Web Vitals optimisation: images, fonts, caching, render path
• Security hardening and automated backups
• On-page SEO: schema, sitemaps, meta, heading structure
• Editor training so your team can update content without breaking layout
• Plugin audit — removing what is slowing you down

What is included in the starting price

Everything below is in the $80 figure. Nothing here is quoted as an extra once the build is underway, which is the point of publishing it.

• Up to six pages, mobile-first responsive build
• Enquiry forms with spam protection and reliable delivery
• On-page SEO and schema markup
• Search Console and analytics setup
• Deployment, SSL and domain configuration
• Editing instructions written for whoever will use it
• 30 days of snag fixes after go-live

What costs extra, and why

A quote that omits these is not cheaper — it is less honest. Each one is real work that someone has to do, and pretending otherwise is how a fixed price becomes a negotiation in week two.

Additional pages beyond six

Priced per page, and cheap once the design system exists.

WooCommerce

A store is an e-commerce build rather than a business site — different scope, different quote.

Content writing and photography

I will brief what is needed. Producing it is separate.

Migration from another platform

Content, URLs and a redirect map so the rankings survive the move.

Ongoing maintenance

Updates, backups and security patching, monthly.

How the work runs

1. Audit or plan. For a rebuild, I audit what is there first. For a new build, we plan the page structure around the searches you want to win.
2. Design. Mobile-first layouts you approve before a line of theme code is written.
3. Build. A lean custom theme. Every plugin has to justify its weight.
4. Optimise. Speed and SEO are part of the build, not a phase afterwards that never gets budget.
5. Train. A recorded walkthrough of how to edit your own site.

Day by day

3 days from the day scope is signed off. Published as a schedule rather than a promise of speed — you should be able to tell on day three whether a build is on track.

The technology

Deliberately boring, and that is the feature. A stack another developer can pick up is worth more to you than one that impresses other developers.

CMS

WordPress, kept close to core rather than buried under a page builder

Theme

A lean custom or minimal-child theme. No multipurpose theme carrying 400 features

Forms

Server-side handling with authenticated email delivery

Performance

Caching, modern image formats, and no plugin loading on pages that do not use it

Hosting

Your existing cPanel is usually fine. I will tell you when it is not

What it integrates with

• Google Business Profile and local listing alignment
• Analytics, cookieless by preference so no consent banner is needed
• Email delivery through your own authenticated domain
• Booking or calendar tools where you already use one
• Review collection into the post-job follow-up
• Any documented REST API where the site needs to talk to something else

What I need from you

Short list, and the first item matters most. Projects do not usually slip because the code was hard — they slip because a decision waited a week.

• Page content, or a decision to use what exists on the current site
• Photographs of real work — stock imagery is visible as stock imagery
• Your logo and brand assets, if they exist
• Domain and hosting access, in your name
• One person who can approve the design without a committee

Content and photography

Six pages of honest, specific copy beats twenty pages of filler in both directions: buyers read it and search engines rank it. The pages that matter are the services you actually sell, not an "our values" page nobody opens.

Photographs of your own work are worth more than any design decision I could make. A trades site with twelve real job photos outperforms a beautiful one with stock imagery, because the photos are the proof and the design is only the frame.

Performance standards

Targets, not aspirations — measured before handover on a throttled mobile connection rather than on a fast laptop.

Accessibility standards

This site is built to the same standard it sells, and the accessibility statement lists what is conformant and what is not — which is the part most statements leave out.

Security practices

The SEO included in every build

Not an upsell. A site that launches unindexed is a shop with the shutters down, and the work below is cheap during a build and expensive afterwards because the fixes are structural.

Ownership and handover

You own everything: the domain registered to you, hosting in your account, code in a repository you control, and the payment provider account in your business name. Credentials are handed over as they are created rather than at the end.

A supplier who resists this is protecting recurring revenue rather than your interests. If you want the reasoning in full, including how to check your current site, there is a guide on it.

Aftercare and what happens after launch

Thirty days of snag fixes are included. A snag is something that does not work as scoped — not a new feature, and the difference is written down before launch rather than argued about after it.

You also get written handover documentation aimed at whoever maintains the site next, which may well not be me. That is deliberate: the test of a good handover is whether another developer could take over without calling me, and on my projects they can.

Ongoing maintenance

Optional, monthly, cancellable. Nothing here is required to keep what you paid for.

Payment terms

How this compares to the alternatives

Including the routes that do not involve me, because a comparison that only flatters the author is not a comparison.

What could go wrong, and how it is handled

Content is not ready

The most common cause of a slipped launch on a three-day build. Flagged before we start.

Plugin conflict after an update

Kept unlikely by keeping the plugin count low, and recoverable because backups are configured at launch.

You outgrow WordPress

Possible, and fine. Your content exports cleanly, which is one reason not to bury the site in a proprietary page builder.

Nobody keeps it updated

A real security risk. Either take the retainer or follow the written instructions — but do one of them.