The Security Company That Had Tried Multiple Redesigns. This One Worked. - Iqram Ahmed - UX/UI Expert, Designer, Developer & Team Leader
← All Case Studies
Branding · Web 2023

The Security Company That Had Tried Multiple Redesigns. This One Worked.

They'd had the website redesigned before. More than once. A potential client had nearly hired a competitor because the site made them question whether IMMS was still in business.

Type Branding · Web
Year 2023
Role Product Designer · Developer
Platform WordPress · Custom theme
Read 2 min
Project visual

IMMS Security had SSAIB certification, real expertise, and a strong track record protecting homes and businesses across Edinburgh. Their website communicated none of it. Previous redesigns had improved the visuals without fixing the underlying problems — confusing service navigation, a mobile experience that loaded slowly and felt unfinished, and no clear signal of credibility for visitors who didn't already know the company. In a category where trust is everything and the decision to hire a security firm is not casual, a website that made people uncertain was actively losing business. One potential client told them they had nearly gone to a competitor because the site made them question whether IMMS was still operating.

The previous redesigns had treated this as a visual problem. It wasn't. I spent time understanding how people actually make decisions about security services — and it's not primarily about price or even service range. It's about trust signals arriving fast enough to keep someone on the page. Homeowners want reassurance and simple pricing. Business owners want to see expertise validation before they'll request a quote. The site needed to serve both without conflating them, and it needed to do it quickly — 70% of traffic was coming from mobile, on connections that had no patience for a slow build. Every structural and performance decision followed from that.

I built a custom WordPress theme from scratch rather than adapting a previous build or using a page builder. The previous redesigns had used off-the-shelf solutions that created performance debt. A 1.2 second average load time — against a typical 3 to 4 seconds for comparable sites — required clean, hand-coded HTML, CSS, and JavaScript with no plugin overhead. For a site where credibility is established in the first few seconds, load time is a trust signal, not a technical detail.

We created separate paths through the site for residential and commercial visitors rather than presenting a single service list. Mixed audiences seeing undifferentiated content assume the product isn't quite right for them. Homeowners and business owners have different risk profiles, different questions, and different decision timelines. Routing them separately reduced the cognitive load of finding relevant information and increased the likelihood of a contact form submission.

Trust signals were treated as structural requirements, not design embellishments. The SSAIB certification, coverage map, real customer photography, and response time guarantees were placed where users needed reassurance — at decision points in the journey, not grouped on an about page. This was the decision previous redesigns had missed: credibility information placed where it looks good versus placed where it actually changes behaviour.

40%

higher conversion rate from visitor to lead within three months of launch

Visitor-to-lead conversion increased 40% within three months. Website traffic grew 47% over the same period. The site ranked number one on Google for security services in Edinburgh. Average load time came in at 1.2 seconds against a category average of three to four seconds — a Lighthouse score above 95 confirmed the performance baseline. The less quantifiable outcome was the shift in client type: IMMS began receiving enquiries from larger commercial clients who had found them through search. The website had repositioned them from a local option to the credible choice in their market.

I wrote the conversion-focused content alongside the design rather than after it, which worked well here. What I'd do differently is establish a clearer content brief with the client earlier — some of the service descriptions went through unnecessary rounds of revision because we hadn't agreed on the tone and reading level before design started. On a trust-critical site like this, content decisions and design decisions are the same decision. They should start at the same time.

Get in touch

If you are working on something
that needs this kind of thinking,
I would like to hear about it.