Conversion Research Sprint
Funnel analysis, session replays, heatmaps, on-site polls and user tests across your top revenue templates. Output is a ranked list of friction points with revenue attached.
Dubai, UAE
Conversion Rate Optimisation in Dubai
In Dubai the biggest conversion problem is usually not the add-to-cart button — it is the Arabic path and the payment method nobody tested.
Delivered remotely for brands across Dubai and United Arab Emirates.
Grow · Dubai
Why Dubai brands come to us for this
- Conversion baseline split by language, because the Arabic path is usually the weaker number and nobody has looked
- Tests judged on delivered and paid orders, not checkout completions, so COD failure cannot flatter a winner
- Address entry rebuilt for a market with no postal codes — building, area and landmark fields the courier can actually use
- Delivery promise, cutoff time and returns wording treated as primary conversion elements, not footer content
- Test windows planned around Ramadan's late-night traffic shift rather than run straight through it
Most CRO programmes in this market test one version of the store and report one number, which hides the fact that you are running two experiences with different conversion rates. The Arabic path almost always converts worse, and not because Arabic-speaking buyers are less willing — because the mirrored layout has a broken component nobody has looked at, or because the trust content, the size guidance and the returns policy were only ever written properly in English. Splitting the baseline by language is usually the first honest number we produce.
The second is the payment mix. A store where most orders arrive as cash on delivery does not have a conversion problem so much as a completion problem: the checkout completes, the delivery fails, the cash comes back, and the reported conversion rate was never real. We test against delivered, paid orders rather than checkout completions, which changes which variant wins surprisingly often. Prepayment incentives, wallet and instalment placement, and the wording around delivery and returns are all testable levers on that share.
Then the ordinary friction, which here has an unusual shape. Address entry is the standout: a checkout built for postal codes fights a market that does not use them, and shoppers who cannot describe their building in the fields provided either abandon or enter something the courier cannot use, which becomes a failed delivery a week later. Delivery promise matters more than price for a lot of Dubai buyers — same-day and next-day are the local norm, so a vague estimate reads as a risk. And Ramadan shifts traffic to late-night hours, which means a test running across it is measuring two different populations unless you plan for that.
Local context
Testing a store that has two directions and two audiences
Research in Dubai has to be done twice. Session recordings and heatmaps on the English store tell you nothing about where the Arabic layout breaks, and the Arabic recordings routinely show the same handful of failures: a filter drawer that opens off-screen, a quantity stepper whose plus and minus are reversed, a price and currency that render in the wrong order, a form field that jumps direction when the user types Latin characters into an Arabic form. We run the research pass on both, then we prioritise tests against the audience segment they affect. The population itself is another split worth respecting — Dubai is majority expatriate, and a store's buyers can span Emirati nationals, long-term South Asian residents, Western expats and GCC visitors shopping during a Dubai trip, all with different payment habits and different expectations about delivery. Reporting one blended rate across all of them tells you almost nothing you can act on.
Scope
What Conversion Optimisation includes
The same standard of work we run for every client — applied to a Dubai brand’s realities.
Full service detailPrioritised Test Roadmap
Every hypothesis scored on impact, confidence and effort, with the projected revenue and required sample size stated up front. You always know what runs next and why.
Experiment Build & QA
Tests built and QA'd across devices, browsers and your app stack, with flicker-free rendering and no measurable hit to Core Web Vitals.
Statistical Analysis
Pre-declared sample sizes, sequential-testing guardrails and segment-level readouts by device, traffic source and new versus returning. No peeking, no calling a test at 80%.
Checkout & Cart Optimisation
Cart drawer, shipping thresholds, payment options, express checkout placement and post-purchase upsell, tested against AOV and revenue per session rather than clicks.
Monthly Programme Report
Tests run, results in full, cumulative revenue impact and what the results taught us about your customers. Losers are reported in the same detail as winners.
Scoped and quoted for your Dubai store
We do not work off a rate card. Every Dubai engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedHow it runs
From kickoff to results
Measure
We instrument the funnel properly first. Most stores have broken or double-counted events, and you cannot optimise against numbers you cannot trust.
Research
Quant tells us where visitors leave. Qual tells us why. We combine analytics, replays and direct customer input before writing a single hypothesis.
Prioritise
Hypotheses are scored and sequenced so the highest-value, lowest-effort tests run first. The roadmap is shared and you can reorder it.
Test
Two to four concurrent experiments depending on traffic, each run to a pre-declared sample size. No test gets stopped early because it looks good on day three.
Implement & Compound
Winners get hard-coded into the theme, losers get documented, and every result feeds the next round of hypotheses. The programme gets smarter each month.
Proof
Conversion Optimisation results
Anonymised under NDA. Figures pulled from the client’s own analytics.
Premium Skincare (DTC)
8-figure DTC brand, ~140 SKUs, US + CA · Shopify Plus (migrated from Magento 2)
Magento 2 cost $9k a month in hosting, extensions and emergency dev before a single feature shipped. Mobile LCP sat at 5.4 seconds and mobile converted at less than half the desktop rate across 68% of sessions. The named constraint: 11,412 indexed URLs and a top-3 organic position on their hero category, so a migration that lost rankings would cost more than the platform ever saved.
+41%mobile conversion rate1.62% to 2.28% over the first 90 days post-launch
5.4s → 1.8smobile LCP75th-percentile CrUX field data, not lab
+27%organic sessionssix months post-migration vs. pre-migration baseline, branded queries excluded
$108k/yrplatform cost removedhosting, extension licences and the standing emergency dev retainer
Performance Apparel (DTC)
~$6M/yr DTC, 900+ SKUs across size and colour variants, US · Shopify Plus
Returns ran at 31% and refund cost consumed the entire paid media margin. One size chart image served 40 different fits, and 62% of add-to-carts started on a collection page that never showed variant availability. The named constraint: no new product photography budget, so every fix had to come out of the existing asset library and the review corpus.
+29%sitewide conversion rate1.71% to 2.21%, five-month average
+14%average order value$84 to $96 once the threshold bar and cross-sell shipped
31% → 22%return ratenine-point drop, roughly $310k/yr in recovered margin
1.9x → 2.4xblended MERwith paid spend held flat throughout
In their words
Clients on this work
CVR 1.9% → 2.7%
“We'd been running our own tests for a year and calling every 3% swing a win. The first thing they did was tell us our sample sizes were garbage, which was not a fun call to sit through. Six months later we're getting wins that actually hold up when you re-measure them. Sitewide CVR went from 1.9% to 2.7%.”
Founder & CEOApparel DTC brand, ~$12M/yr · Los Angeles, CA
Verified client, 2025FAQ
Conversion Optimisation in Dubai — your questions
Two, once you have the traffic for it. They are different populations with different friction and often different devices, and a blended result hides the segment where the fix was needed. If volume only supports one test at a time, run it on whichever language carries more revenue and treat the other as a research and fix track rather than a testing track.
Incrementally, and always measured on delivered revenue. Typical tests are a small prepayment incentive, moving wallets and instalment options above COD in the payment list, adding delivery-tracking reassurance earlier in the journey, and setting an order-value threshold above which COD is not offered. Removing it outright is the one change we would not test first in this market — it usually costs more orders than it saves.
It can invalidate it. Buying hours move dramatically toward the post-Iftar evening and late night, purchase intent changes category by category, and a test that started before Ramadan and finished during it has measured two different audiences. We either close experiments before it begins, or deliberately run Ramadan-specific tests inside it and analyse that window on its own.
A required postal code field, or an address form that offers no sensible way to enter a building name and area. It looks trivial and it produces two separate losses: buyers who abandon at that step, and buyers who type something arbitrary to get past it, which becomes a failed delivery and a refunded COD order later. Fixing it is cheap and usually the first thing on the list.
Around 40,000 sessions and 800 orders a month is where a testing programme becomes statistically viable. Below that, tests take months to reach significance and you are better served by research-led redesign work and analytics fixes. We will tell you honestly which bucket you are in.
The first test goes live in week three, after research and instrumentation. Meaningful cumulative impact typically shows around month four, once six to ten tests have run. CRO is a compounding programme, not a one-month fix, and anyone promising otherwise is selling best practices.
Some do, and that is normal. A loser is still information: it rules out a hypothesis and sharpens the next one. We report losses in the same detail as wins because a programme that only ever produces winners is one that is not being measured properly.
Next step
Conversion Optimisation for your Dubai brand.
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Shopify or Shopify Plus stores doing $150k/mo or moreFounder, CEO or eCommerce lead on the callNo deck and no pitch — we open your store instead
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.