invivox.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, TikTok and Google Maps and others), adding 4.5 MB and 704 ms of main-thread time.

Reduce initial server response time. Google estimates savings of 808 ms on a phone.

The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

strapiapp.com costs a phone 0 ms of main-thread work and 2.3 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.

crisp.help costs a phone 92 ms of main-thread work and 1.3 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.

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

Google Maps costs a phone 133 ms of main-thread work and 328 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.

Your server takes 908 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 26.7 MB in 300 requests on a phone: images 22.4 MB (139), fonts 2.2 MB (32) and scripts 1.6 MB (80). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example 17913641666ac60c46b62174.22840508.png at 3,872 px wide, shown at 589 px. Resized copies would save about 14.8 MB.

6 images weigh 14.1 MB together. On a phone connection a single image that size takes seconds.

39 images (19.0 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.

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

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

106 elements hidden from screen readers can still receive keyboard focus.

Links must have discernible text: 14 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

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

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 18 elements on the page fail this check, rated minor by axe-core.

Your title is 77 characters, so Google will cut it off around 60: “Formation Médicale - Leader du partage de connaissances entre pairs – Invivox”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“L’échographie au cabinet : toutes les clés pour v…”, “Pédiatrie & Neurologie : Les essentiels cliniques…” and “Vos collègues partagent leur expertise”). One clear main headline is easier for people and search engines.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 113 pages on invivox.com 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://invivox.com/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.

Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://invivox.com/fr/training/detail/BIOX86940/tdah-troubles-du-sommeil-l-usage-de-la-melatonine-en-pratique-cli, whose canonical is https://invivox.com/fr/training/detail/BIOX86940. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://invivox.com/fr/training/detail/CREG16459/reflux-constipation-diversification-evaluez-votre-pratique-en-gas, https://invivox.com/fr/training/detail/INMG96014/prescription-des-antidepresseurs-en-pratique-clinique, https://invivox.com/fr/training/detail/SANV84797/prevention-vrs-2026-2027-les-recommandations-a-connaitre, https://invivox.com/fr/training/detail/IXDZ85506/tdah-en-medecine-generale-diagnostic-et-facteurs-de-risque, https://invivox.com/fr/training/detail/BIOX30413/tdah-chez-l-enfant-quelle-place-pour-les-traitements-pharmacologi and https://invivox.com/fr/training/detail/ECHO74212/echographie-au-cabinet-cout-formation-reglementaire-le-guide-pour and 4 others took over 3 s to send their HTML from our server.

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

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.

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

Social proof on the homepage: 36 customer or partner logos. 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.

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 3,092 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Microsoft Clarity and TikTok 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 11 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.