mnemopro.fr website review

38 files are served with short cache lifetimes, so returning visitors download them again (1,019 KiB).

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

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

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

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

About 167 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.

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

Google CDN costs a phone 238 ms of main-thread work and 743 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.

3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 894 KiB and 266 ms of main-thread time.

8 KiB could be saved by minifying CSS.

3 long tasks block the main thread while loading, the longest for 73 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.

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

Your largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

4 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.

Your homepage downloads 2.2 MB in 61 requests on a phone: scripts 958 KiB (24), images 617 KiB (14) and other files 352 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example slider-1-2.jpg at 1,920 px wide, shown at 482 px. Resized copies would save about 139 KiB.

2 images (352 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.

3 images further down the page (89 KiB) 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 0.63 g of CO₂e: 75.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

3 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 8 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

Headings skip levels (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 meta description is 181 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.

No XML sitemap at https://mnemopro.fr/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at mnemopro.fr/robots.txt, the first file search crawlers ask for.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 46 pages on mnemopro.fr and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://mnemopro.fr/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://mnemopro.fr/les-principes, https://mnemopro.fr/les-principes/organisation, https://mnemopro.fr/les-principes/classement, https://mnemopro.fr/les-principes/controle, https://mnemopro.fr/les-principes/rappel and https://mnemopro.fr/les-principes/archivage and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://mnemopro.fr/les-principes, whose canonical is https://mnemopro.fr/les-principes/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mnemopro.fr/les-principes, https://mnemopro.fr/les-principes/organisation, https://mnemopro.fr/les-principes/classement, https://mnemopro.fr/les-principes/controle, https://mnemopro.fr/les-principes/rappel and https://mnemopro.fr/les-principes/archivage and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mnemopro.fr/modules and https://mnemopro.fr/la-technique 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 14 pages linked from your homepage and read each the way a search engine does.

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

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

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

Large scripts ship without source maps.

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

Social proof on the homepage: 15 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 796 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.