Lorrain Chauffage & Climatisation

A heating, air conditioning and plumbing company in the Centre region of France, with callouts seven days a week. The trade imposes a constraint few sites handle properly: some visitors arrive in an emergency, from a phone, looking for one thing only, a number that answers.

The others are preparing an installation project, comparing, and reading. Two opposite audiences on the same site, and you have to serve both without the first being slowed down by the second.

A home page that unfolds in one piece, plus four service pages and a blog. The call button is one gesture away from anywhere on the site, with no need to scroll back up.

The site already existed in an earlier form. Rather than rewrite it, we brought it as it was into our technical foundation. It is a deliberate engineering choice: it gains version control, a security baseline, a test environment and automated deployment, without redoing a design that worked.

Then a full pass on performance, search visibility and accessibility, which is where the gain was clearest.

Bespoke is not always graphic. Here it lay in the engineering: the deployment foundation had to be adapted to the particular way this site works, by removing the steps that had no place in it.

Accessibility was treated as a quality requirement, not a box to tick. Contrast measured rather than eyeballed, tap targets sized for a thumb, explicit labels rather than icons alone, a journey usable from the keyboard.

That work serves everyone. Sufficient contrast does not only help someone with poor sight: it helps the person checking their phone in bright sunlight, on a building site.

Lighthouse mobile reading of 21 August 2026, median of three runs on the live site.

Performance 86. Accessibility 100. Best practices 100. Server response time around 0.30 seconds, no visual shift, blocking time around 70 milliseconds.

The search score shown is deliberately low: the site is in acceptance testing and closed to search engines, which drags that indicator down. That is normal and it reverses at launch.

New reading on 8 September 2026: response time 0.13 seconds. We publish these figures because anyone can verify them, which is the only good reason to publish a figure.

An accessibility score of 100 out of 100 is not a trophy. It is the guarantee that no visitor runs into an avoidable obstacle, on a site where part of the traffic arrives in an emergency.

Speed plays the same role. Someone whose boiler has failed on a Sunday does not reload a slow page: they call the next result.

And the editorial structure, with its separate service pages and its blog, serves local search, which is the only lever that counts for a company whose work is regional.

The site existed, in a technical form different from the one we usually use. The reflex answer would have been to rewrite it to our standard. We did not.

The design worked and the client knew it. Rewriting it would have cost weeks for a visually identical result, and would have introduced regressions where there were none. So we brought it into our foundation as it was, adapting the foundation rather than the site.

What the client concretely gains: version control, a security baseline, a test environment separate from production, and automated deployment with the ability to roll back. All of that without paying for a rewrite.

It is the kind of decision that separates a supplier from an order-taker. Rewriting would have been more comfortable for us and more expensive for him.

Thirty-one pieces of feedback received from the client, twenty-seven handled and awaiting sign-off as we write. We publish that figure because it says something useful about the way we work.

A project that receives no feedback is not a successful project, it is a project the client has not looked at. Thirty-one pieces of feedback on a site this size is a sign of engagement, and it is exactly what we set out to provoke by opening a structured acceptance process rather than asking for blanket approval.

Every piece of feedback is a ticket, with a status the client can see and a link to the fix once it is handled. Nobody has to remember anything, and nothing gets lost between two conversations.