The Moroccan mobile experience
A large share of traffic runs on mobile networks of uneven quality, on entry-level and mid-range phones. A three-megabyte page of images that feels fine on wifi can take eight seconds on degraded 4G.
The consequence is direct: the heavier the page, the higher the abandonment rate. On a pay-per-click campaign, every lost second is budget spent without contact.
Causes of slowness, by impact
First images: uncompressed files, dimensions larger than display size, legacy formats. Then third-party scripts accumulated over the years (pixels, widgets, chatbots, embedded maps) that block rendering. Then unnecessarily loaded fonts, and finally slow or badly cached hosting.
Animations count too: a few CSS effects cost almost nothing, but a heavy animation library can delay rendering by hundreds of milliseconds.
Fixes that show visible results
Convert images to WebP or AVIF, cap real dimensions to display size, prioritise above-the-fold rendering, defer the rest, and place a cache in front of the server. These four actions give the best effort-to-result ratio.
Script cleanup often means deleting: a widget visitors never use, an obsolete pixel, a Google map loaded on every page instead of the contact page only.
Measuring honestly
Use PageSpeed Insights and always test the mobile version, on the homepage and an inner page. A score is not a business result: what matters is time until main content appears and visual stability.
Be wary of anyone promising an exact score before starting. Scores depend on hosting, network, third-party scripts and device. Serious work delivers before/after measurements with the device and test context.