Summary of work — 19 June 2026 · Prepared by BrightSite
In the last 48 hours we carried out a round of improvements to calliope-interpreters.org — covering search visibility, a few design and display fixes, the mobile experience, page speed, your cookie-consent setup, and the contact page. This note summarises what is now live.
We made a series of refinements to strengthen how the site performs in search across your six languages:
The result: each language version is better positioned in its own market.
Hero images. On the inner pages, the large header images had grey patches in the bottom corners instead of clean white up to the curved edge. That is now corrected — below is the conference-equipment page before and after.
Before — grey corners
After — clean to the curve
“Examples from our portfolio.” This section had picked up some placeholder content — a stray “@username”, a one-star rating and a social icon that were never meant to appear. We restored the intended design: the event title as a heading beside its description, with none of the clutter.
On phones, the language selector used to sit as a large orange bar above your main image, pushing your content down the page. We moved it neatly into the menu, so the first thing visitors see is your content. It now sits at the bottom of the menu when opened.
We have enabled next-generation image delivery (WebP), which automatically serves smaller, faster-loading versions of your images to modern browsers. This improves load times, particularly on mobile.
We reworked the Contact pages across all six languages and moved the newsletter sign-up out of the footer into its own place beside the enquiry form. See the Contact-page changes and rationale →
We added an llms.txt file to your site — a structured index, a little like a sitemap but written for AI assistants. It helps tools like ChatGPT, Claude and Perplexity find and accurately summarise your services across all six languages, so when someone asks an AI about conference interpreting, your site is easier for it to represent correctly.
While reviewing the site we found that the cookie-consent banner was not actually controlling your analytics — visitor tracking was running before anyone made a choice. We wrote custom code to handle this properly, and it is now live:
This has been tested and verified across regions before going live. As it touches data-privacy obligations, we would still recommend having your usual privacy or legal contact confirm that the final approach suits your requirements.
We have placed your site's custom code under proper version control — a safeguard that means every change is now tracked and recoverable. This is, in fact, what lay behind the portfolio display issue noted earlier: an earlier customisation had been quietly lost, and version control prevents that from recurring.
That completes this round of improvements — the full before/after performance figures are on the Performance page. Please do let us know if you have any questions.