neomind.ma website review

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

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

6 images could be 278 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).

1 long task block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.

2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 60 KiB and 26 ms of main-thread time.

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

7 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

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

Your largest element takes 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Optimiser les systèmes informatiques Obtenez votre audit gr…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4-Types-of-Digital-Transformation-Projects.webp weighs 522 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.9 MB in 304 requests on a phone: images 2.1 MB (17), fonts 454 KiB (230) and scripts 222 KiB (35). Under 2 MB keeps phones on slow connections fast.

7 images further down the page (381 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example How-Digital-Transformation-is-Driving-Customer-Experience.jp at 1,448 px wide, shown at 360 px. Resized copies would save about 36 KiB.

6 images (371 KiB) 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.

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

1 button has no accessible name, so screen readers announce just “button”.

All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 20 characters: “Accueil - neomind.ma”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 456 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 70 pages on neomind.ma and 0 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://neomind.ma/shop has no meta description, so Google writes the search snippet from whatever text it finds.

https://neomind.ma/about-us and https://neomind.ma/about-layout-two use the same meta description. A description written for each page earns more clicks.

https://neomind.ma/about-us, https://neomind.ma/about-layout-two, https://neomind.ma/about-layout-three, https://neomind.ma/about-layout-four, https://neomind.ma/about-layout-five and https://neomind.ma/about-layout-six and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://neomind.ma/' was loaded over HTTPS, but requested an insecure font 'http://neomind.…”.

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

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

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 445 words of visible text.

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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.