natachaoceane.com website review

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

YouTube costs a phone 2.8 s of main-thread work and 7.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

15 images could be 848 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (YouTube, Shopify and Other Google APIs/SDKs and others), adding 8.3 MB and 3.0 s of main-thread time.

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

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

177 KiB JavaScript is shipped twice across bundles.

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

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

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

10 KiB could be saved by minifying JavaScript.

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.

Polyfills for old browsers add 3 KiB JavaScript that modern phones do not need.

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

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

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

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

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

12 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-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 14.0 MB in 359 requests on a phone: scripts 7.4 MB (95), images 4.2 MB (53) and other files 809 KiB (137). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example HIIT._carousel_image_1_1024x.png at 1,024 px wide, shown at 247 px. Resized copies would save about 359 KiB.

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

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

There are 32 <h1> headlines (“”, “HYBRID. Training Guide” and “HYBRID. + Recipe Guide Bundle”). One clear main headline is easier for people and search engines.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 40 pages on natachaoceane.com and 13 external pages.

https://natachaoceane.com/products/cut-2023-new and https://natachaoceane.com/products/cut-new all use the title “CUT. – Natacha Oceane”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://natachaoceane.com/pages/recipe-guides has no meta description, so Google writes the search snippet from whatever text it finds.

https://natachaoceane.com/products/cut-2023-build-reload-bundle and https://natachaoceane.com/products/build-reload-cut-2023-bundle use the same meta description. A description written for each page earns more clicks.

https://natachaoceane.com/pages/recipe-guides has no <h1> headline, so visitors and search engines get no clear main topic.

https://natachaoceane.com/products/cut-2022-new and https://natachaoceane.com/products/cut-new took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 741 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 9 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.