Case Study

BayanTech: six multilingual WordPress sites for a localization group

Six Arabic and English WordPress brand sites for a translation and localization group, built from Figma designs, and a main site whose real-user load time fell by 40 percent during 2022.

Client
BayanTech, a translation and localization company working in 120+ languages
Industry and market
Translation and localization; UAE, Saudi Arabia, South Africa and Egypt
My role
Web Developer, in-house (2022): built six multilingual brand websites
Duration
January to December 2022
Stack
WordPress, Elementor, ACF, PHP, WPML (Arabic and English), Figma
Live site
bayan-tech.com

The business problem

BayanTech sells translation and localization to global brands, so its own websites are its storefront. A group of related brands needed websites that looked consistent, worked in Arabic and English, and could be edited by a marketing team that was not technical. The main BayanTech site was also slow for real visitors: in early 2022, three in four phone visits took 6.3 seconds or longer to show the main content.

The technical challenge

  • Six sites, one design language. Each brand needed its own look but shared components and editing patterns, so one developer could keep all of them consistent.
  • Multilingual from day one. Arabic and English with correct right-to-left layouts, language switching and translated metadata.
  • Design fidelity. The designs came from Figma and had to be matched closely, including spacing and typography in both directions.
  • Speed. Fast pages on mobile, which is where many visitors arrive.

What I did

I built six multilingual WordPress brand websites, including BayanTech, AsiaLocalize, SawaTech and 700apps, translating Figma designs into custom themes with Elementor and ACF and WPML for the two languages. Structured ACF fields kept the editors’ work predictable, and I worked on the front end of the main BayanTech site to reduce load time, with 90+ PageSpeed Insights scores as the target on the key sites.

Results

Real-user data from the Chrome UX Report for bayan-tech.com, at the 75th percentile, January to December 2022. These figures cover the whole site and reflect every change made to it in that period, not only mine.

  • Phone LCP fell from 6.3 s to 3.8 s (about 40% faster); desktop LCP from 5.6 s to 2.9 s (about 48% faster).
  • Phone server response time (TTFB) fell from 4.4 s to 1.8 s.
  • Fast phone page loads almost doubled, from 12% to 23%, and slow desktop loads fell from 23% to 7%.

“Our multilingual site used to crawl. Amr re-engineered the front end, fixed our Core Web Vitals, and the faster pages now turn far more visitors into qualified translation-quote requests.”

Mona Adel, Marketing Director, BayanTech

What I would do differently

A phone LCP of 3.8 s is better but still above the 2.5 s “good” threshold. With more time I would go further on image weight and the Elementor output, which is usually the largest remaining cost on sites like these.

Is your multilingual site slow?

If your sites serve more than one language and your team edits them without a developer, a technical assessment shows what is slowing them down and what to fix first. See also speed and Core Web Vitals work.

Related services

Facing something similar?

Send me the link and a few lines. I reply within one business day with a clear next step.

Tell me about your site

Share the constraints, launch pressure, and technical scope.

  • Current stack or platform
  • Key integrations or APIs
  • Timeline and delivery constraints
  • The highest-risk technical unknown
Prefer a call or WhatsApp? Add your number (optional)