Case study · bilingual corporate website

Oplinx Solutions

We designed and built a bilingual English/Arabic website for a Beirut consultancy — full RTL support, self-contained, and fast on any connection.

UI/UXWeb development
Start a project Visit oplinx.netlify.app
Oplinx Solutions bilingual consultancy website designed and built by kaprera
Oplinx Solutions — bilingual consultancy website by kaprera
/ Overview

The challenge

Oplinx needed a credible first presence that speaks to clients across the MENA region in both English and Arabic — and explains four distinct consulting practices without overwhelming a first-time visitor.

The solution

We designed and built a single-scroll bilingual site with a full RTL layout switch — clear service architecture, industry coverage, and a direct contact path — shipped as self-contained static HTML.

/ What we built

Inside the project.

  • Bilingual English/Arabic interface with a full right-to-left layout switch
  • Four service practices — strategy, operations, smart digital solutions, and branding
  • Industries, founder's insight, and success-story sections that build trust before the ask
  • Contact section with an enquiry form plus direct phone and email
  • Self-contained static build — no frameworks, no third-party scripts or trackers
  • Hardened HTTP response headers — CSP, HSTS, and frame & MIME-type protection
/ Specs
Type
Bilingual corporate website
Stack
Static HTML, CSS & JavaScript
Client
Consultancy firm — Beirut, Lebanon
Scope
UI/UX design & web development
/ Results

The outcome.

EN / عFully bilingual with RTL support
100%Responsive across devices
Asecurityheaders.com grade
/ Measured

Measured, not claimed.

Every figure below is a real reading from a standard tool anyone can re-run — Google Lighthouse for speed and quality, the W3C validators for the code itself. Each one says what it means for you in plain language.

Google Lighthouse scores out of 100

98PerformanceHow quickly the page becomes usable. Google scores it out of 100 — 90 and above counts as fast.
100Accessibility A11Y · WCAGHow well the page works for people using a screen reader, a keyboard, or high-contrast settings — checked against the WCAG standard.
100Best practices BPWhether the site follows the modern rules of the web — HTTPS everywhere, safe libraries, and no errors thrown in the browser.
100SEOHow readable the page is to search engines — titles, descriptions, crawlable links and valid robots rules.

Loading & responsiveness Core Web Vitals

0.5 sFirst contentful paint FCPHow long before the visitor sees anything at all. Under 1.8 seconds is the target.
0.5 sLargest contentful paint LCPWhen the main image or headline has finished loading — the moment the page looks ready. Google wants this under 2.5 seconds.
0 msTotal blocking time TBTHow long the page ignores taps and clicks because it is still busy loading. Zero means it never freezes on the visitor.
0Cumulative layout shift CLSHow much the page jumps around while it loads. Zero means nothing moves under the reader's finger mid-tap.
0 msInteraction to next paint INPHow fast the page answers a tap. It is measured on real visitors over time; the lab stand-in shown here is total blocking time.

Code quality & weight standards, size, dependencies

18 KBHTML, compressed GZIP / BRThe weight of the page's own code as it actually travels over the network. Smaller is cheaper and faster on mobile data.
Not neededFont preloadWhether the custom typefaces are requested up front, so text never flashes in a fallback font before settling.
0W3C HTML errorsErrors found by the W3C's official markup validator. Zero means the code is standards-clean, which is what keeps a site working through future browsers.
0W3C CSS errorsThe same official check applied to the stylesheets. Invalid CSS is where most cross-browser display bugs begin.
0Third-party originsHow many outside servers the page pulls from. Every one is another company that can slow the page down, break it, or track your visitors.

Measured on the live site at oplinx.netlify.app with Google Lighthouse 12.8.2 (desktop) and the W3C validators, August 2026.

/ More work

More case studies.

Bayader Investments case study by kaprera Bayader Investments Corporate website War Action Research case study by kaprera War Action Research Interactive research platform Agri Pro Services case study by kaprera Agri Pro Services Internal operations platform
/ Let's build something

Want results like these?

Book a call See more work