sourceo.net website review

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

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

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

About 949 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 573 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

Facebook costs a phone 890 ms of main-thread work and 340 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.

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

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

Polyfills for old browsers add 61 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

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

25 KiB could be saved by minifying CSS.

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

Real visitors wait 616 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Your largest element takes 30.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Optimisez votre gestion RH et Paie Talenteo est une solutio…”.

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

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

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

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

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

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

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

21 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-31, real Chrome visitors' largest content (lcp) went from 4.1 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.3 MB in 361 requests on a phone: scripts 2.8 MB (119), images 814 KiB (70) and fonts 762 KiB (22). Under 2 MB keeps phones on slow connections fast.

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

There are 5 <h1> headlines (“Un SIRH intelligent pour les entreprises en crois…”, “Un SIRH intelligent conçu pour les entreprises en…” and “Offrez la meilleure expérience collaborateur”). One clear main headline is easier for people and search engines.

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

The homepage links to 85 pages on sourceo.net and 8 external pages.

https://talenteo.com/a-propos-partenariat-2 and https://talenteo.com/a-propos-partenariat all use the title “Solution Complète de Paie et Gestion RH - Talenteo”. Search engines can't tell which page to show for a search, so each competes with the others.

https://talenteo.com/blog-talenteo has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

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: 16 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.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 18 cookies, 9 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.