Case studies.
Lebanese Spotlight
A full UI/UX with integrated backend workflow tools for volunteer onboarding and program management.
Read case study
Agri Pro Services
A custom, role-based operations platform: live dashboard, client and deal pipelines, and field reporting.
Read case study
Oplinx Solutions
A bilingual English/Arabic consultancy website with a full right-to-left layout switch, self-contained and fast on any connection.
Read case study
Ana Arabia
A fast, responsive landing page for Riyadh Season, with a cinematic hero and a layout that mirrors between Arabic and English.
Read case study
Bayader Investments
A responsive corporate website that is image-led, fast, and easy for the firm to manage itself.
Read case study
War Action Research
An interactive research platform built around a clickable world map that surfaces research on global conflict and its impact on women, children and youth.
Read case study
Mr. Ibrahim Hussein
A teaching platform for a programming tutor: published courses, every exercise in both C++ and Java, and a scored evaluation test.
Read case study
AL-Shamaa Engineering
A bilingual English/Arabic landing page for an engineering consultancy that does reinforcement detailing, BIM and structural design, illustrated entirely in hand-drawn SVG.
Read case study
Mono Collector
A Shopify storefront in build, with the catalogue, the product pages and the checkout journey designed as one piece.
Case study to follow at launchVyné Flowers
A flower delivery store on Shopify: a 257-product catalogue with size, colour and gift add-on variants, built for senders abroad ordering into Lebanon.
Case study to follow at launchWhat ongoing support looks like.
These are averages across the five client sites we currently maintain. Not the best score of the five, the mean of all of them. Every figure is measured with the same tools we use on the individual case studies.
Mean of Lebanese Spotlight, Agri Pro Services, Oplinx Solutions, Mr. Ibrahim Hussein and AL-Shamaa Engineering, measured with Google Lighthouse 12.8.2 (desktop) and the W3C validators, August 2026.
A site is not finished when it launches.
Those numbers are not what the sites scored on launch day. They are what they score now, because someone has been watching them since.
Browsers ship every few weeks
Chrome and Safari update constantly. Something that renders correctly today (a layout, a form, a checkout step) can break quietly months later, and nobody files a bug. Someone has to keep looking.
Google keeps moving the line
The thresholds behind these scores get revised. INP replaced FID as a Core Web Vital in 2024. A perfect score is a reading from one day, not a permanent state.
Dependencies age into vulnerabilities
Every framework, plugin and library accumulates published security advisories. Left unpatched, a site becomes a public list of known ways in.
Content is what slows a site down
Launch figures are measured on an empty site. Real ones fill up with unoptimised images, embeds and marketing tags, and that is where the seconds come from.