Improving our own website: the KEELBLOOM case study
INTERNAL CASE STUDY · 23 OCTOBER 2026
We applied a straightforward method to our own website: identify an inconsistency, make a targeted correction and check the result through to the end of the enquiry journey.
This case covers two practical points: displayed currencies and contact-message delivery. The website is KEELBLOOM’s own; this documents work on our business, not a project delivered for a client.
01 / UNDERSTANDING PRICES
A consistent currency for each language version
The finding
The English website combined euro budgets with a currency selector and explanations of dirham conversion. Visitors had several different pricing references to interpret.
The published correction
The French version displays euro budgets; the English version displays US dollars. Amounts are rounded up to the next ten. The quote confirms the scope, taxes and final total before approval.
Check performed: amounts and currency wording were reviewed across the checked pages, bundles, sample quotes and relevant forms. The conversion basis for English budgets is explained on the website.
See it live: budgets in English · budgets in French.
02 / RECEIVING ENQUIRIES
Follow a message all the way to the inbox
The finding
The first tests reached the inbox, but a sender-authentication check flagged an issue: the website’s sending server was missing from the domain’s SPF setting.
The published correction
The Infomaniak sending service was added to the SPF setting while retaining the existing authorisations. Three further tests, including both submissions from a real phone, then passed SPF, DKIM and DMARC checks.
Check performed: on-screen confirmation, storage in WordPress, delivery to the contact inbox and checks for duplicates. Phone number and budget remained optional in the detailed brief.
The French and English tests from the real phone arrived at 12:18 and 12:20 Abu Dhabi time. No duplicates were observed for these tests.
THE CHECKS BEHIND THE CASE
Exactly what was tested
| Journey | Conditions | Result |
|---|---|---|
| Simple contact form | Desktop · French and English | 2 messages received |
| Detailed brief | Desktop · French | 1 message received |
| Detailed brief | Simulated 320 px mobile view · French and English | 2 messages received |
| Check after the SPF correction | Desktop · French | 1 message received |
| Simple contact form | Real phone · French and English | 2 messages received |
All eight tests were recorded and their notifications received, with no duplicates observed. Confirmations were checked during testing, with feedback from Laurent for the real-phone test.
How the findings are documented
File versions from before and after the currency correction have been retained. The contact checks are supported by the stored test enquiries, received notifications and email-authentication results after correction. These technical records remain internal to protect access to the administration area and mailbox.
FOR YOUR WEBSITE
Start with a specific problem.
A confusing price, an uncertain form or an unclear next step? Tell us what concerns you. We will clarify the need, then agree the scope and quote before you commit.
Discuss a website improvement ↗An audit identifies priorities. Implementing corrections is quoted separately.
Understand the audit scope →