rivieramaison.com website review

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

The page goes through 6 redirects before it starts loading, costing about 1.8 s. Link and advertise the final URL directly.

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

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 3.4 MB and 967 ms of main-thread time.

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

YouTube costs a phone 330 ms of main-thread work and 1,014 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.

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

Google Tag Manager costs a phone 305 ms of main-thread work and 604 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.

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

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.

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

bedigital.ai costs a phone 49 ms of main-thread work and 1.2 MB 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.

2 KiB could be saved by minifying JavaScript.

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

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

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.

For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.

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

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hello autumn Ontdek de nieuwe collectie”.

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

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

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

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

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

3 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-24, real Chrome visitors' tap response (inp) went from 127 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.3 MB in 144 requests on a phone: scripts 3.5 MB (53), images 336 KiB (15) and stylesheets 223 KiB (30). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 148.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 image has no alt text, which hurts accessibility and image search.

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

Links do not have a discernible name (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 18 characters: “Human verification”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://rivieramaison.com/sitemap_index.xml, so Google discovers your pages only by following links.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

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://rivieramaison.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.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console during Google's test (“Access to font at 'https://urbancotton.nl/wp-content/uploads/sites/4/2024/10/Poppins-Light.ttf' fro…”).

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 61 words of visible text; thin pages give Google and first-time buyers little to go on.

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.