kodiko.fr website review

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

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

8 third-party services load with your homepage (YouTube, website-files.com and Hotjar and others), adding 2.0 MB and 1.0 s of main-thread time.

Your mobile performance score is 52 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

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

YouTube costs a phone 510 ms of main-thread work and 984 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.

5 files are served with short cache lifetimes, so returning visitors download them again (100 KiB).

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

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

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

website-files.com costs a phone 170 ms of main-thread work and 733 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.

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

Your largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Le premier programme de mentorat "réfugiés-salariés" en ent…”.

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

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

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

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

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

10 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.4 MB in 62 requests on a phone: scripts 1.4 MB (20), images 544 KiB (18) and HTML 187 KiB (4). Under 2 MB keeps phones on slow connections fast.

60f0009745789a72206e9a43_img-hero-kodiko.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

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

There are 5 <h1> headlines (“Le premier programme de mentorat "réfugiés-salari…”, “10 ans de rencontres, 70 parcours : Kodiko dévoil…” and “La taxe d'apprentissage pour Kodiko”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

The homepage links to 54 pages on kodiko.fr and 22 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://kodiko.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://kodiko.fr/territoires/paris and https://kodiko.fr/territoires/strasbourg all use the title “Kodiko”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://kodiko.fr/territoires/paris and https://kodiko.fr/territoires/strasbourg have no meta description, so Google writes the search snippet from whatever text it finds.

https://kodiko.fr/nos-resultats and https://kodiko.fr/qui-sommes-nous use the same meta description. A description written for each page earns more clicks.

https://kodiko.fr/blog/10-ans-de-rencontres-avec-kodiko has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 23 found) 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.

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

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.

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

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

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