The problem
Mounifull had a working storefront and a real catalogue, but the data showed visitors were bouncing before reaching product detail pages, and the support inbox was full of repeat questions about specs, sizing, and availability that the site was not answering. Mobile traffic (over 70% of visits) had a noticeably worse path to checkout than desktop — a problem on a Lebanese site, where mobile is the primary surface.
The root issues fell into three buckets: the bilingual experience felt bolted-on rather than native; the CTA hierarchy was flat (every button competed equally for attention); and the checkout flow had too many cognitive steps for mobile-first shoppers who do not want to fill long forms on the phone.
The solution
We rebuilt the catalogue and checkout layers around three principles: language parity, single-action-per-screen on mobile, and information surfaced where the question is asked.
Key features
- Native bilingual experience. Full English and Arabic content with right-to-left layout that feels native to Arabic users, not translated. Persistent language preference.
- Sharper CTA hierarchy. One primary action per screen, secondary actions visually demoted. Add-to-cart and "view details" stopped competing.
- Mobile-first checkout. Reduced form steps, persistent cart on every page, address auto-suggest, and Lebanon-aware payment options surfaced clearly.
- Inline answers to repeat questions. Sizing, materials, shipping windows, and return terms moved into the product page itself, dropping support load.
- Performance pass. Image compression, lazy loading, and a slim CSS footprint so the site loads under 2 seconds on Lebanese 4G.
Process
Two weeks of analytics review and customer-support transcript reading to identify the exact friction points (not assumed ones). Two weeks of design with bilingual mocks reviewed with native Arabic speakers. Four weeks of build, then a two-week phased rollout starting with the highest-traffic categories.
Tech stack
HTML5, CSS3, vanilla JavaScript, mobile-first responsive design, English/Arabic bilingual implementation. The architecture was kept light so non-developers on the team can update content without breaking layout.
Outcome
Measured against a 4-week pre-launch baseline:
- +24% add-to-cart actions, driven primarily by the clearer CTA hierarchy and the inline question-answering on product pages.
- +18% checkout-start rate, coming from the slimmer mobile checkout flow.
- -35% support response time, because fewer repeat questions arrived — the site was now answering the questions support used to handle one-by-one.
Bonus: bounce rate on Arabic traffic dropped meaningfully once the language parity was real, expanding the addressable market without any additional ad spend.
What this build is good for
This pattern fits Lebanese retailers (food, fashion, home goods, beauty) who already have a working catalogue but watch the analytics tell them mobile is leaking. It is not about replatforming — it is about a focused conversion overhaul layered on top of what is working. Most rebuilds we run on this template land between $1,200 and $4,500 depending on catalogue size and bilingual depth.