olybe.com website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

Your mobile performance score is 70 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, website-files.com and cookiebot.eu and others), adding 1.7 MB and 611 ms of main-thread time.

6 images could be 403 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.

Google Tag Manager costs a phone 441 ms of main-thread work and 494 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 254 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

website-files.com costs a phone 73 ms of main-thread work and 998 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 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.

About 17 KiB of CSS is downloaded but never applied on this page.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Application de yoga, pilates en ligne comme en studio.”.

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

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

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

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

69c51b6f6503463271f6d86d_mockup-app-p-500.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).

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

Banner 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 banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

Your title is 78 characters, so Google will cut it off around 60: “Olybe : Yoga, Pilates #ForAll - Cours en studio et en ligne de Yoga et Pilates”.

There are 2 <h1> headlines (“Yoga & Pilates, à la maison ou en studio” and “Yoga & PilatesSuivez votre flow où vous le souhai…”). One clear main headline is easier for people and search engines.

Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.

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

There is no https://www.olybe.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.

1 error was logged to the browser console while the page loaded, for example “[components] Finsweet Components - this Component is not available for production use. Please purchase a plan at https:…”.

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.

Social proof on the homepage: 2 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 500 words of visible text.

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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