ironshark.fr website review

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

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

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

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

8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 1.9 MB and 667 ms of main-thread time.

Shopify costs a phone 348 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.

About 427 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

17 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying CSS.

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.

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

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

Real visitors wait 226 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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 204 ms to 235 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.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 359 requests on a phone: images 1.4 MB (43), scripts 1.3 MB (110) and other files 968 KiB (139). Under 2 MB keeps phones on slow connections fast.

d2c333f4-93e5-49a8-8102-399a2050ea52.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 further down the page (38 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.9 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.

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

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

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

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

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

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is 71 characters, so Google will cut it off around 60: “Iron Shark : compléments alimentaires et nutrition sportive – IronShark”.

The homepage links to 180 pages on ironshark.fr and 10 external pages.

https://www.ironshark.fr/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.ironshark.fr/collections/all and https://www.ironshark.fr/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.ironshark.fr/collections/all, https://www.ironshark.fr/customer_authentication/redirect, https://www.ironshark.fr/collections/tous-nos-produits and https://www.ironshark.fr/collections/nutrition-digestion have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ironshark.fr/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ironshark.fr/customer_authentication/redirect and https://www.ironshark.fr/products/shark-rice-cream took over 3 s to send their HTML from our server.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelector')”.

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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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