space23.it website review

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

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

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

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

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

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

ZenDesk costs a phone 130 ms of main-thread work and 394 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.

8 third-party services load with your homepage (ZenDesk, Google Tag Manager and Cookiebot and others), adding 986 KiB and 333 ms of main-thread time.

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

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

1 image could be 16 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.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

Scripts block taps and scrolling for 387 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-31, real Chrome visitors' tap response (inp) went from 129 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 239 requests on a phone: scripts 1.8 MB (116), other files 680 KiB (80) and images 390 KiB (21). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (25 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 0.91 g of CO₂e: 108.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

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

1 link inside paragraphs relies on colour alone to stand out.

Some list items are not inside a list.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

Headings skip levels (h1 → h6, h1 → h6 and h1 → h6), which makes the page harder to scan with a screen reader.

Your title is 81 characters, so Google will cut it off around 60: “Space23 | Scarpe Sportive, Accessori e Abbigliamento Sportswear | Marco Materazzi”.

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

There are 5 <h1> headlines (“CARHARTT”, “OBEY” and “THE NORTH FACE”). One clear main headline is easier for people and search engines.

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

3 links have no real href, so search engines can't follow them.

The homepage links to 117 pages on space23.it and 5 external pages.

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.

https://www.space23.it/pages/support-and-informations, https://www.space23.it/collections/sneakers, https://www.space23.it/collections/urbanstyle-abbigliamento, https://www.space23.it/collections/men, https://www.space23.it/collections/women and https://www.space23.it/pages/brands and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.space23.it/pages/support-and-informations, https://www.space23.it/collections/sneakers, https://www.space23.it/collections/urbanstyle-abbigliamento, https://www.space23.it/collections/men, https://www.space23.it/collections/women and https://www.space23.it/pages/brands and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.space23.it/collections/accessori and https://www.space23.it/collections/basketball took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to fetch”.

Large scripts ship without source maps.

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

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

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 8 cookies (measured from a US location before any click).

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