Why loading speed decides part of your sales
Much of Morocco’s web traffic arrives over 4G on mid-range phones. Here is how to make your mobile website fast in the conditions visitors really face.

A site tested at the office always feels fast. It is served over a stable connection, on a recent machine, with a warm cache. The real visitor opens your page from the back of a petit taxi, on patchy 4G, on a three-year-old phone with twelve tabs open.
That is the visitor you need to serve. The good news is that whatever slows them down can usually be fixed without rebuilding the site.
The real cost of waiting
Visitors do not leave at a steady rate: they drop off in steps. A page that stays blank for a few seconds looks broken, and the reflex is to go back to the search results and tap the next link. That link often belongs to your competitor.
On a booking site, the loss happens before the offer has even been read. On a shop, it happens at the worst moment, between basket and payment, when the confirmation page is slow to respond. And during an ad campaign it costs you twice, because the click has already been paid for.
What Google measures
Google sums up the loading experience in three metrics, the Core Web Vitals, based on real visits from Chrome users:
- LCP (Largest Contentful Paint): how long the largest visible element takes to appear, often the main photo or the headline. Good is 2.5 seconds or less.
- INP (Interaction to Next Paint): the delay between a gesture, such as tapping a button or opening a menu, and a visible response on the page. Good is under 200 milliseconds.
- CLS (Cumulative Layout Shift): how stable the layout stays while loading. Good is under 0.1.
These metrics are part of Google’s ranking signals, though their weight is modest next to the relevance of your content. Their main value lies elsewhere: they describe fairly accurately what a visitor in a hurry feels. You can check yours for free in PageSpeed Insights, or in the Core Web Vitals report in Search Console.
Where the weight comes from, in order
Images
Almost always the biggest item. A 4 MB photo straight off the camera, displayed in a 600-pixel-wide frame, is carrying mostly wasted data. The fix is well known: a modern format (WebP or AVIF), dimensions matched to each screen size, sensible compression, and lazy loading for anything below the fold. Riads and restaurants, which live on their photography, are hit hardest.
Fonts
Three families and six weights means six files to download before the text displays properly. Two weights are almost always enough. If the site also runs in Arabic, pick a typeface that covers both scripts, or load the Arabic font only on the pages that need it.
Third-party scripts
Every widget adds a request, often a blocking one: live chat, Meta pixel, Google Ads tag, interactive map, cookie banner, embedded video, review badge. One at a time they seem light. Together they can outweigh the site itself. An embedded Google Map, for instance, can be swapped for a clickable image that opens the app: the visitor gets the same thing, without the weight.
Layout shifts
A block that loads late and pushes the button away just as you tap it: that is exactly what CLS measures, and exactly what infuriates users. The usual causes are familiar. Images with no declared dimensions, promotional banners injected at the top of the page, fonts that change size as they load.
Hosting
A slow or poorly configured server adds a delay before the first byte even arrives. For an audience that is mostly Moroccan and European, hosting in Western Europe or behind a CDN gives decent response times. Add server-side caching and switch on compression, and that part of the problem is solved at modest cost. The cheapest shared hosting plans, split between hundreds of sites, are often the hidden reason a site crawls in the evening at peak times.
Sites that sell need extra care
An online shop or a booking site carries more risk than a brochure site: catalogue filters, carousels, ad tracking, a payment module, product reviews. Each piece is justified on its own, and together they end up slowing the pages that matter most.
So we deal with three pages first: the home page, the product page (or room page) and the checkout. For a car hire agency in Marrakech, the About page can wait. The booking form has to respond instantly when a customer picks dates in the arrivals hall at Menara airport, on a congested network, with a suitcase in the other hand.
Our working rule
We test on a mid-range phone over a throttled mobile connection, never only on the office computer. A site ships when it passes that test. We also set a weight budget per page at the start of the project, the same way you would set a financial budget: any new feature has to fit inside it or replace something else.
That discipline has a consequence we fully accept: we turn down animations that cost more than they give.
Decoration should never be paid for by the visitor.
Where to start
- Open your site on your own phone, on mobile data, off the office wifi, after clearing the cache. Time it.
- Run your home page through PageSpeed Insights and look at the mobile tab.
- List the third-party scripts installed and remove any whose data nobody looks at any more.
- Check the file size of your five largest images.
- Test the contact or booking form from start to finish, on a phone.
If the result worries you, a website audit will pinpoint what is weighing the site down and put a cost on the fixes; all of our services build this check in from the design stage.


