promobile.sn website review

29 images could be 22.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

About 755 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

Your mobile performance score is 40 (desktop: 47). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

11 files are served with short cache lifetimes, so returning visitors download them again (9.9 MB).

6 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 11.3 MB and 606 ms of main-thread time.

Amazon Web Services costs a phone 0 ms of main-thread work and 9.9 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

YouTube costs a phone 461 ms of main-thread work and 988 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.5 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google CDN costs a phone 132 ms of main-thread work and 349 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

7 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 858 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.57 (75th percentile). Good is under 0.1.

Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

Your largest element takes 33.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Voix & SMS Restez proches de ceux que vous aimez ! Avec DIS…”.

Visually, the page fills in at 25.1 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 91.8 s. Good is under 3.8 s.

The layout shifts by 0.503 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.5 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 206 ms in total while the page loads. Good is under 200 ms.

8 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 38.7 MB in 111 requests on a phone: images 36.6 MB (38), scripts 1.5 MB (32) and fonts 338 KiB (11). Under 2 MB keeps phones on slow connections fast.

8 images weigh 10.9 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example 5958dc12-98b8-4359-8a02-5e458c38d064.jpeg at 1,920 px wide, shown at 366 px. Resized copies would save about 9.0 MB.

15 images (12.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

11 images further down the page (9.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 10.97 g of CO₂e: 1316.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

22 links have no real href, so search engines can't follow them.

The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.

There is no https://www.promobile.sn/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.promobile.sn/products and https://www.promobile.sn/ouragency have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.promobile.sn/products and https://www.promobile.sn/ouragency have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “[object Object]”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 658 words of visible text.

Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 4 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.