rh-partner.com website review

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

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

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

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

7 third-party services load with your homepage (hsappstatic.net, Hubspot and Google Tag Manager and others), adding 1.1 MB and 646 ms of main-thread time.

About 263 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.

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

hsappstatic.net costs a phone 397 ms of main-thread work and 731 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 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

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

2 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

5 KiB could be saved by minifying CSS.

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

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

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

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

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

Scripts block taps and scrolling for 253 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.

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.3 MB in 158 requests on a phone: scripts 1.5 MB (64), fonts 362 KiB (7) and stylesheets 268 KiB (49). Under 2 MB keeps phones on slow connections fast.

laptop_mockup004.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).

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

2 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: 40 elements on the page fail this check, rated moderate by axe-core.

There are 3 <h1> headlines (“UNE SOLUTION SAAS COLLABORATIVE”, “DES OFFRES SIMPLES, ADAPTÉES A TOUTES LES ENTREPR…” and “Une démonstration live ça vous dit ?”). One clear main headline is easier for people and search engines.

The homepage links to 30 pages on rh-partner.com and 8 external pages.

There is no https://rh-partner.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 https://rh-partner.com/pricings and https://rh-partner.com/contact-us, which answer with an error. Visitors hit a dead end and search engines drop them.

https://rh-partner.com/solution, https://rh-partner.com/about-us, https://rh-partner.com/nous-contacter, https://rh-partner.com/blog, https://rh-partner.com/request-a-demo and https://rh-partner.com/demo have no <h1> headline, so visitors and search engines get no clear main topic.

https://rh-partner.com/nous-contacter, https://rh-partner.com/blog, https://rh-partner.com/request-a-demo and https://rh-partner.com/demo have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

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

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

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.

Social proof on the homepage: 29 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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