WordPress development

WordPress powers a large part of the web because it is easy to start with. The trouble usually arrives later: thirty plugins, a theme edited directly in the admin panel, no staging copy and a page that takes six seconds to load.

We work on both ends of that story. New sites get a theme written for the content, not a bought template stuffed with a page builder, and a set of plugins chosen for what they do rather than for what their landing page promises. Existing sites get an audit first: what is installed, what it costs in queries and requests, and what can be removed without anyone noticing.

What we do:
— custom themes and blocks for the editor, so content people are not afraid to publish;
— plugins for the logic a site actually needs, instead of ten generic ones;
— performance work: caching, images, database, the plugin that calls an API on every page load;
— security and cleanup after a hack, plus updates that stop being scary;
— WooCommerce: catalogue, payments, delivery, migrations between hostings and platforms.

Every site we hand over has a staging copy, a backup that has been restored at least once and a short document explaining how to update it. That is usually the difference between a site that ages well and one that has to be rebuilt in two years.