WordPress development
A WordPress site on a bespoke theme with no page builder — light, maintainable, and structured for search from the first commit.
What you get
- Bespoke theme written against WordPress core, with no page-builder dependency
- A simple editing experience with custom fields for each content type
- Correct heading structure, schema and metadata at the theme level
- Responsive, mobile-first layout with accessibility built in
- Baseline performance work: images, fonts, and minimal script
- A short screen recording covering day-to-day content editing
How it runs
- 1
Define the content model
Before any design work we establish what kinds of content the site has and what fields each one needs. A correct content model makes both SEO and maintenance straightforward.
- 2
Build the theme
The theme is written from scratch and loads only what is used. The result is a page running on tens of kilobytes of CSS and JS rather than several megabytes.
- 3
Hand over and train
The site ships with real content, not placeholder text, plus a short session so you can manage it yourself.
WordPress is not the problem
WordPress did not earn its reputation for being slow on its own. A clean install with a simple theme responds in a few hundred milliseconds. What makes a site heavy is usually this combination: a multipurpose theme written for every kind of site, plus a page builder, plus twenty plugins each doing a slice of what the theme should do.
I start from the opposite end: the theme contains exactly what your site needs.
Content types, not pages
Most projects go wrong at the point where a page is designed rather than a content type. The difference shows up when you add the fiftieth item.
// A defined content type with defined fields, instead of
// hand-arranging the same blocks on every page.
register_post_type( 'project', [
'label' => 'Projects',
'public' => true,
'has_archive' => true,
'rewrite' => [ 'slug' => 'projects', 'with_front' => false ],
'supports' => [ 'title', 'editor', 'thumbnail', 'excerpt' ],
'show_in_rest' => true,
] );Once content has structure, getting it out again — for the site, for schema, for a feed, or tomorrow for a mobile app — is a few lines of work.
What does not go into the theme
- jQuery, unless a plugin genuinely requires it.
- Remote fonts. Fonts are self-hosted and served with
font-display: swap. - A whole CSS framework. Only what is used.
- Tracking scripts in
wp_headwithout checking their effect on INP.
Accessibility is part of the build
AA contrast, visible focus on every interactive element, full keyboard navigation, correct heading order. None of this costs extra time if it is done from the start. Retrofitting it later is close to a rewrite.
Work in this area
Healthcare2026A medical website for orthopaedic surgeon Dr Kamran Kordi
The site needed to build trust, explain orthopaedic services for different age groups, and make booking or direct contact easy without overwhelming patients with generic medical copy.
- Service groups with their own path
- 4
Read the case study
Radiation technology and medical equipment2026A corporate and commerce website for IPAPDA
IPAPDA needed one coherent platform for engineering services, specialist products, training courses and project work, without making visitors choose between corporate content and commerce.
- Value-chain sections
- 5
Read the case study
Curtains and interior decor2026A curtain store front end with catalogue and price estimate form
Buying curtains depends on window size, and customers want to see models and get a rough cost before calling. A page of photos alone leaves both questions unanswered.
- Product categories with their own catalogue
- 4
Read the case study
Office equipment and manufacturing2025A WordPress product site for Golpiran electric stamping equipment
A specialist product such as an electric stamping machine needs clear technical explanation and separate paths for retail buyers, organisations and wholesale partners. A simple product page was not enough.
- Machine models with their own product page
- 2
Read the case study
Frequently asked questions
Why not use a page builder or a bought theme?
For simple sites on tight budgets a page builder is a reasonable choice and I will say so. But if speed and control matter, every page builder adds tens of kilobytes of CSS and JS that cannot be removed.
Can I edit the content myself afterwards?
Yes. All text and images are editable from the WordPress admin. What is locked down is structure and layout — precisely so the site does not degrade over time.
Do you provide hosting and domains?
No, but I will help you choose suitable hosting, and deployment to your host is part of the work.
What if I want to add a shop later?
The theme is written so adding WooCommerce does not mean a rewrite. I plan for it from the start if I know it is on your roadmap.
Related services
Not sure which one you need?
Just describe the problem. Working out which bucket it falls into is my job.