tonsor1951.it website review

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

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

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

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

8 third-party services load with your homepage (Optanon, Google CDN and anglerfox.com and others), adding 1.5 MB and 438 ms of main-thread time.

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

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

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

Google CDN costs a phone 71 ms of main-thread work and 354 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.

anglerfox.com costs a phone 65 ms of main-thread work and 317 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.

2 KiB could be saved by minifying CSS.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “KIT REGALO BARBA”.

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

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

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

15 images 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 100 ms to 87 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.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 4.1 MB in 312 requests on a phone: scripts 1.9 MB (78), other files 1.0 MB (186) and images 804 KiB (24). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Vita-Trattamento-2024_1920x.jpg at 1,800 px wide, shown at 150 px. Resized copies would save about 54 KiB.

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

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

1 text element doesn'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.

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

All page content should be contained by landmarks: 46 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.

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.

4 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.

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

Your title is 84 characters, so Google will cut it off around 60: “Tonsor1951 - Prodotti per cura di Barba, Capelli e Viso | Prova online – Tonsor 1951”.

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

There are 10 <h1> headlines (“KIT REGALO BARBA”, “KIT REGALO CAPELLI” and “Best sellers”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 81 pages on tonsor1951.it and 6 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.

Your homepage links to https://www.tonsor1951.it/pages/store-locator, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.tonsor1951.it/pages/rituale-rasatura and https://www.tonsor1951.it/pages/vision-of-future use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.tonsor1951.it/collections/limited-edition/Limited-Edition, whose canonical is https://www.tonsor1951.it/collections/limited-edition/limited-edition. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tonsor1951.it/pages/diventa-partner has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tonsor1951.it/collections/barba, https://www.tonsor1951.it/collections/rasatura, https://www.tonsor1951.it/pages/rituale-capelli, https://www.tonsor1951.it/pages/rituale-rasatura and https://www.tonsor1951.it/collections/unstoppable-fighters-outfit-capsule-collection/T-SHIRT-UOMO took over 3 s to send their HTML from our server.

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

12 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://sibforms.com/forms/end-form/build/sib-styles.css' from origin 'https://www.tonsor1…”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 442 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 20 cookies, 1 of them by other companies (measured from a US location before any click).

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