Octyva
An engineering contractor whose website did not reflect the size of the projects it delivers. Built with custom code rather than a page builder.
Before.
Industrial clients judge a company quickly. The old website did not show the scale or the technical standard of the work.
The Work.
Custom coded front end
No page builder. A bespoke PHP theme, which is why the pages load the way they do.
Wide layout design system
Built for the scale of industrial project imagery rather than a narrow blog column.
Brand assets integrated
The existing identity carried through properly instead of approximated.
Technical SEO foundation
Structure, schema and performance handled at build time rather than retrofitted.
After.
A website that looks like a serious engineering firm rather than a template, and loads quickly enough to make a good first impression.
How this site
performs.
This is the return on building it by hand. There is no page builder here and no plugin stack, so the browser is not made to parse code written for every site rather than this one. Industrial buyers often open a site from a project office on a weak connection, which is the condition the mobile test simulates, and the page delivers its main content in 2.7 seconds under it. Blocking time is zero, meaning the page never freezes under a tap.
Google PageSpeed Insights, August 2026
Mobile figures are measured on an emulated mid range Android over a throttled 4G connection, which is the harder of the two tests and the one closer to how most people arrive.
Recognise The Problem?
If any of that sounds like your situation, describe it in a few lines. You will get a straight view on whether it is worth fixing and what it would involve.
One reply, from me, within one business day.