A slow site is rarely slow for a mysterious reason. It is slow because of plugin load, uncompressed images and render-blocking scripts, and because nobody measured which of the three costs the most. An ugly site is usually ugly because it was built from a template designed for somebody else’s business.
- Content and publishing sites — structured for scale: silos, templates, internal linking and ad placements designed in from the start rather than retrofitted
- Business and service sites — fast, clear, and built to convert enquiries
- Custom WordPress plugins — for the cases where your requirement does not exist as a product
- Performance work — Core Web Vitals, caching, image strategy, render-blocking resources, and the real-world fixes that move the number
- Migrations — host to host or platform to platform, with redirects mapped and nothing lost
- Maintenance — updates, backups, security and the monthly checks that stop small problems becoming outages
Through code and APIs, not through admin panels
It is faster, it repeats across many sites, and it leaves a record of exactly what changed. For a single page the difference is small. For a hundred pages across six sites, it is the difference between a day and a week.
Every build gets tested end to end on our side — the actual front end in a real browser, not just a database check — and you get a pass or fail report before it reaches you.
We host the pages our own money lands on
When you buy a click and send it to your own page, every hundred milliseconds of load time is money you paid for and did not get to use. Our content properties are built for that: lean templates, ad placements designed in from the start, consent handled correctly, Core Web Vitals measured rather than assumed. A client site gets the same build discipline, whether it sells a product or an idea.
- Audit
What exists now, what is slow, and what is at risk.
- Scope
Pages, templates, integrations and dates, in writing.
- Build
In staging, through code, with the content structure settled first.
- Test
Real browser, real devices, pass or fail per check.
- Launch and maintain
Redirects mapped, then updates and monitoring.
What you get
- A published, responsive site with the pages, forms and integrations agreed
- Core Web Vitals measured and passing on launch, with the numbers
- Schema, metadata and sitemap in place so search and AI engines can read it
- Maintenance within the agreed scope and period
Outside our control
- Domains, hosting, email and third-party subscriptions unless included in writing
- Payment gateway approval and marketplace rules, which those providers decide
- Legal page wording — we draft it, you or your advisor review it; it is not legal advice
Scope, deliverables, timelines and fees go in writing before work starts. Ad spend, platform fees and third-party subscriptions are billed separately from our fee.
Businesses with a site that is slow, dated or hard to update, publishers who need a site built for scale, and anyone who has been told their requirement needs a custom plugin.
Do you work on an existing site or only new builds?
Both. A large share of our work is fixing and speeding up sites someone else built.
Can you make my site faster without a rebuild?
Usually yes. Most slow WordPress sites are slow for reasons that are all fixable in place.
Who owns the code and the hosting?
You do, including any plugins we write for you. No lock-in.
Do you use page builders?
Only where you need to edit the page yourself. Otherwise we build lighter, because every builder adds weight.
What do you build on?
WordPress with custom, performance-tuned themes, PHP, JavaScript, Cloudflare Workers and Shopify. We list what we use daily; if a project needs something else, we say so rather than claim it.
Start with the audit
We look at what you have now and tell you what is costing you money. You get the findings whether or not you hire us.