Web development articles
Performance, ecommerce architecture and platform choices, measured on real rebuilds.
These are engineering notes written for the person who has to sign off the build rather than the person who has to write the code, though there is enough detail here for both.
Two themes run through everything. Performance is an architecture decision, not a plugin: almost every site we inherit has a caching layer bolted onto a structure that guaranteed it would be slow. And platform choice matters far less than the decisions made before the platform question comes up, such as what the catalogue really looks like, who edits content, and what happens in month thirteen when the promotional rules change.
We work across Next.js, WordPress, Laravel and Shopify, so we have no incentive to sell you one of them. Where an article recommends something it says what it is recommending against, and why.
Numbers in these pieces come from client work: median Core Web Vitals before and after, build times, the actual cost of a bad decision. We do not publish client names without permission, but every figure is one we measured.
Start with the twelve rebuilds if the site is slow, or the ecommerce piece if you are about to choose a platform.
Start here 2
Need this done?
We build and rebuild sites on Next.js, WordPress, Laravel and Shopify: fixed scope, published rates, and a performance budget written into the contract.
Web development servicesWhat actually moves Core Web Vitals: twelve rebuilds measured
Twelve client rebuilds, measured over eighteen months. Four changes account for most of the improvement, and the rest was noise. Here are the numbers.
One email a month. What we shipped, what broke, what we learned.
No list-building tricks. Unsubscribe is one click and we do not ask why.
Reading is cheaper than rebuilding twice.
Send us the URL. We will tell you which of these articles applies to your site, which one you can ignore, and what we would fix first.