rejence.fr website review

About 763 KiB 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.

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

11 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 (rebuyengine.com, Klaviyo and Google Tag Manager and others), adding 2.2 MB and 843 ms of main-thread time.

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

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

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

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

rebuyengine.com costs a phone 185 ms of main-thread work and 330 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,093 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

join-stories.com costs a phone 122 ms of main-thread work and 815 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.

Klaviyo costs a phone 157 ms of main-thread work and 323 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.

Shopify costs a phone 127 ms of main-thread work and 349 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 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.

32 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Feme de dos sous une douche, tenant le soin lavant apaisant…”.

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

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 265 requests on a phone: scripts 1.8 MB (101), other files 778 KiB (104) and media 672 KiB (1). Under 2 MB keeps phones on slow connections fast.

femme-douche-soin-lavant-apaisant-epaule.webp 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).

1 image is downloaded at several times the size a phone draws it, for example DREJ24-REJENCE_LOGO_QUADRI_23c75376-21eb-4d9c-a640-19aaa6549 at 1,654 px wide, shown at 100 px. Resized copies would save about 56 KiB.

1 image (426 KiB) is 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.17 g of CO₂e: 141.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Elements must only use permitted ARIA attributes: 9 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

5 images have no alt text, which hurts accessibility and image search.

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

13 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

The homepage links to 259 pages on rejence.fr and 5 external pages.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'protect' of object '#<Object>'”.

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

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.

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

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