myconnecting.fr website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 3.2 MB and 1.4 s of main-thread time.

32 images could be 726 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

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

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

Google Tag Manager costs a phone 377 ms of main-thread work and 772 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.

The page has 2,217 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Hubspot costs a phone 146 ms of main-thread work and 404 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.

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

About 63 KiB of CSS is downloaded but never applied on this page.

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

22 KiB could be saved by minifying JavaScript.

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.

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.

Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Télécharger le catalogue 2026”.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 124 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.0 MB in 203 requests on a phone: scripts 3.4 MB (57), images 1.3 MB (59) and fonts 1.1 MB (9). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example logo_fiducial-1_resized.png at 1,313 px wide, shown at 66 px. Resized copies would save about 144 KiB.

6 images (322 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 1.99 g of CO₂e: 239.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

2 links inside paragraphs rely on colour alone to stand out.

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

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (3 elements).

There are 4 <h1> headlines (“Humain. IA. RSE”, “Transformation des équipes Learning : Aligner la …” and “Santé mentale et IA”). One clear main headline is easier for people and search engines.

The homepage links to 129 pages on myconnecting.fr and 12 external pages.

Your Organization JSON-LD is missing url, 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.

There is no https://myconnecting.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://myconnecting.fr/pole-humain-et-rse, https://myconnecting.fr/pole-ia-data-et-digital and https://myconnecting.fr/langues-et-interculturel all use the title “Formation Sur Mesure | Apprentissage Personnalisé”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://myconnecting.fr/pole-humain-et-rse, https://myconnecting.fr/pole-ia-data-et-digital and https://myconnecting.fr/langues-et-interculturel use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://myconnecting.fr/formations/langues/categorie/thematique:48, whose canonical is https://myconnecting.fr/formations/langues. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://myconnecting.fr/a-propos/entreprise-a-mission has no <h1> headline, so visitors and search engines get no clear main topic.

https://myconnecting.fr/formations/softskills, https://myconnecting.fr/formations/management-leadership and https://myconnecting.fr/formations/ia took over 3 s to send their HTML from our server.

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

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 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 1,358 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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 19 cookies (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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.