Loading
Web Development6 min read
Speed is not a setting you switch on at the end. It is a set of decisions made throughout the build.
Most slow websites were not built badly. They were built without speed as a requirement, and then asked to be fast afterwards. By that point the expensive decisions have already been made — which is why speed is a build requirement in our website development work, not a post-launch fix.
Search engines assess page experience using three signals, measured on real visitors rather than in a lab.
That last one is the most irritating for users and the easiest to fix: it is almost always an image or an advert without reserved space, pushing content down as it loads.
On most business websites, four things account for nearly all the weight.
A modern build is not one that uses the newest framework. It is one that ships less: pages rendered ahead of time where they can be, JavaScript only where interaction genuinely needs it, and no library included for a feature the platform now provides.
The fastest code is the code that was never downloaded.
Speed helps, but the larger part is whether the content can be understood. One clear subject per page. A single H1 that says what the page is. Headings in order. Descriptive links rather than "click here". Alt text that describes the image. Structured data so a machine knows what it is looking at. This is the ground floor of technical SEO, and it is decided during the build.
None of that is exotic. It is ordinary discipline applied consistently, which is why so many sites miss it.
Run your homepage and one service page through PageSpeed Insights, and read the field data section rather than the lab score — that is real visitor experience. Then open your site on a phone on mobile data and try to find your own phone number. Those two checks will tell you more than any audit document.
Get in touch
Tell us what you need. We will come back with questions, an approach and a price.