ioelamamma.com website review

About 564 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

8 third-party services load with your homepage (Hotjar, Shopify and productessentials.app and others), adding 21.9 MB and 400 ms of main-thread time.

Shopify costs a phone 140 ms of main-thread work and 21.7 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.

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

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

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

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

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

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

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

8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

7 KiB could be saved by minifying JavaScript.

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

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

6 KiB could be saved by minifying CSS.

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 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Il nostro sito utilizza i cookie per migliorare la tua espe…”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 23.5 MB in 282 requests on a phone: media 20.9 MB (1), scripts 1.1 MB (66) and other files 975 KiB (158). Under 2 MB keeps phones on slow connections fast.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Your title is 66 characters, so Google will cut it off around 60: “Io e la mamma | Abbigliamento 0-16 anni | Premaman – io e la mamma”.

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

Your <h1> is empty.

The homepage links to 107 pages on ioelamamma.com and 3 external pages.

https://ioelamamma.com/collections/nuovi-arrivi, https://ioelamamma.com/collections/quotidiano-neonato-0-24-mesi, https://ioelamamma.com/collections/quotidiano-bambino-3-7-anni, https://ioelamamma.com/collections/quotidiano-ragazzo-8-16-anni, https://ioelamamma.com/collections/quotidiano-neonata-0-24-mesi and https://ioelamamma.com/collections/quotidiano-bambina-3-7-anni and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ioelamamma.com/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0927/0925/7599/files/logo__trasparente.png?v=1751439321.

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://ioelamamma.com/cdn/shop/t/2/assets/barra-scorrevole-lion.css?v=3294' because its M…”.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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