WordPress on a theme written by hand, not dragged together.
Haryes builds WordPress sites on custom-coded themes instead of Elementor, Divi or WPBakery. The result is a site that loads in under two seconds, survives core updates without breaking, and gives editors a clean interface tied to how your content is actually structured.
The trouble was never WordPress. It is everything piled on top.
Most WordPress sites in Kenya are built the same way: a marketplace theme, a page builder, and a stack of plugins to fill the gaps. It ships quickly and it demos well.
Six months later the same three problems show up.
- Eight-second loads on a mid-tier Android phone.
- A core update that breaks the layout.
- Editors fighting a canvas full of drag handles.
Five stages, each with something you can hold us to
Every stage ends with a deliverable in writing, not a status update.
Discovery
What you publish, who edits it, how often.
A written scope and a fixed price.
Content model
Every page type mapped to real CMS fields.
Editors fill in fields, not layouts.
Theme build
Templates written by hand, no page builder.
Only the code each page needs.
Staging & QA
Tested on a mid-tier Android, on mobile data.
Core Web Vitals checked before launch.
Launch & handover
Go live, train the team, hand over the code.
A site and a repository you own.
Numbers written into the contract, not the pitch deck
Measured on a mid-tier Android over a Kenyan mobile connection, before launch and after.
- Largest Contentful Paint
- <2s
The main content is on screen in under two seconds.
- Page weight
- <800KB
Everything the page downloads, images included.
- JavaScript
- <150KB
Script shipped to the browser, per page.
Budget commitments on every Haryes WordPress build
Content model first
Every build starts from how your content is actually structured.
So the editor screen matches the page, field for field.
Templates written by hand
No Elementor, Divi or WPBakery layer between your content and the browser.
The front end ships only the CSS and JavaScript the page uses.
Every update staged
Core, plugin and PHP updates land on staging before they touch the live site.
Nothing breaks in front of your customers.
Speed treated as a budget
LCP under 2 seconds and page weight under 800KB, agreed up front.
If a feature breaks the budget, we tell you before we build it.
A builder adds weight to every page. Caching cannot remove it.
A builder adds a layer of CSS and JavaScript to every page, whether the page uses it or not. Each plugin added to fill a gap adds more.
Past a point, no amount of caching gets the page back under budget. The weight is in the builder itself.
So we write the theme by hand instead. The front end ships only what the page needs. It passes Core Web Vitals, survives WordPress core and PHP upgrades without a redesign, and gives editors a clean interface.
WordPress, or something else?
One question decides it: how often does the site change? We tell you which fits before you commit.
WordPress
Your team publishes news, insights, listings or events frequently, without a developer.
Build my WordPress siteCustom static site
A small site that rarely changes is faster and cheaper to run without a CMS at all.
See custom buildsWooCommerce or Shopify
Selling products needs a store: WooCommerce or Shopify, with M-Pesa checkout and delivery zones built in.
See store buildsWhat lands in your hands at launch
Four deliverables on every WordPress build. See what a build costs in KES.
Custom theme
Built for your content model.
No builder licence to renew- Templates written for each page type
- Custom fields that mirror your content
- Only the CSS and JavaScript each page needs
Editor training
Your team publishes without us.
Live session + written guide- Walkthrough of every content type
- A short guide your next hire can follow
- Publishing, media and user roles covered
Staging environment
Every change tested first.
Never tested on the live site- A private copy of the site for testing
- Core, plugin and PHP updates checked there
- Pushed to live once approved
Code you own
Structured data and a full repository.
Your domain, hosting and code- Schema wired into the site-wide graph
- Legible to search engines and AI systems
- The full codebase in a repository you own
A WordPress site is not finished at launch
The questions clients ask before signing.
Can you rebuild my existing WordPress site?
Yes, without losing your content, URLs or rankings. Every existing URL is mapped and redirected in a single hop, and the switch is timed to minimise disruption.
Who looks after the site after launch?
Updates need applying and testing, backups taken and verified, and security monitored. We offer this as a monthly maintenance plan, or set your team up to run it in-house.
How do we get started?
Send your requirements through the contact page. You will get a fixed scope and a fixed price before any work begins.
Starting fresh, or rescuing a builder site?
You need a site your team can publish to without calling a developer.
Start with a scope. It is fixed before any work begins.
Build my WordPress siteYour builder site is slow, fragile, or both.
We rebuild the theme and keep your content, URLs and rankings. Need it looked after too? See WordPress maintenance.
Rebuild my siteWordPress is a good CMS buried under too many builders. We take the builder away, so your site stays fast and your team stays in control.
