Skip to main content

WebCraft: Build and Fix Better Websites

WebCraft is about the unglamorous work that makes a website feel good: fast pages, clear structure and a build you can still update six months from now.

We test the tools and the fixes on real sites, not benchmark pages. A speed score is only useful if the page still looks right on a mid-range phone.

How we test websites

We measure load time on a throttled connection, then check layout stability and tap targets on a budget phone. A page that scores well but jumps around while loading is not fast in any way a reader cares about.

We also test the editing experience. If updating a headline takes five clicks and a plugin, the site will go stale. Maintenance is part of performance.

Speed without breaking design

Most slow sites are not slow because of one dramatic problem. They are slow because of many ordinary ones: oversized images, too many fonts, render-blocking scripts and a plugin for every small feature.

We prefer fixes that remove work rather than hide it. Compressing images and deleting unused scripts beats buying another optimisation plugin that adds its own weight.

Builders and hosting

No-code builders have closed much of the gap with custom sites, but the trade-off has moved. The question is no longer whether you can build it; it is whether you can export it, move it and keep it fast as it grows.

We check ownership terms, export options and what happens to your content if you stop paying. Those are the details that decide whether a platform is a tool or a trap.

How to use these guides

Start with the biggest bottleneck, not the longest checklist. Fix images first, then scripts, then fonts. Measure after each change so you know what actually helped.

For neutral technical background, the web.dev performance guides explain the metrics without selling a product. They are a useful reference before you hire anyone.

Latest WebCraft guides