cashlab.fr website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and usemessages.com and others), adding 1.8 MB and 1.0 s of main-thread time.

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

Google Tag Manager costs a phone 521 ms of main-thread work and 881 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 454 ms of main-thread work and 520 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.

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

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

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

Cloudflare CDN costs a phone 4 ms of main-thread work and 314 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.

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

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

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

Polyfills for old browsers add 14 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.

Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ce site web stocke des cookies sur votre ordinateur. Ces co…”.

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

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

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

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

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

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.7 MB in 76 requests on a phone: scripts 1.6 MB (22), other files 353 KiB (19) and fonts 338 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example IMG_7846-scaled.jpg at 2,560 px wide, shown at 56 px. Resized copies would save about 77 KiB.

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

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

All page content should be contained by landmarks: 70 elements on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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 viewport tag blocks pinch-zoom, which low-vision visitors rely on.

There are 2 <h1> headlines (“Expertise et Technologie au service de votre trés…” and “Expertise and Technology at the service of your t…”). One clear main headline is easier for people and search engines.

The homepage links to 200 pages on cashlab.fr and 16 external pages.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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.

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

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

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

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