spartoo.com website review

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

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

12 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 183 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

22 KiB could be saved by minifying CSS.

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

5 third-party services load with your homepage (Google Tag Manager, Bing Ads and Google CDN and others), adding 203 KiB and 107 ms of main-thread time.

1 long task block the main thread while loading, the longest for 79 ms. During a long task the page ignores taps.

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.

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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 layout shifts by 0.843 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

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

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

26 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 90 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 62 requests on a phone: images 2.6 MB (45), scripts 311 KiB (8) and fonts 149 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

18 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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://www.spartoo.com/sitemap.gz, 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.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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 has only about 22 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.