uala.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.0 s faster on a phone.

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

4 images could be 284 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 31 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Stripe and awswaf.com and others), adding 1.8 MB and 1.4 s of main-thread time.

Google Tag Manager costs a phone 871 ms of main-thread work and 894 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.

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

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

awswaf.com costs a phone 145 ms of main-thread work and 303 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.

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

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

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

Desktop scores 64 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

5 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Utilizziamo i nostri cookie e quelle di terze parti per per…”.

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

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

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

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

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

The layout shifts by 0.161 while loading, so content jumps under the reader's thumb. Good is under 0.1.

2 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-17, real Chrome visitors' tap response (inp) went from 305 ms to 327 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.1 MB in 77 requests on a phone: scripts 2.4 MB (30), images 414 KiB (12) and other files 93 KiB (25). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example v2.i17534911.w1851.h780.x24F18440.png at 1,851 px wide, shown at 275 px. Resized copies would save about 177 KiB.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 68 characters, so Google will cut it off around 60: “Prenota online parrucchiere, estetista, unghie, massaggi - Treatwell”.

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

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 50 pages on uala.it and 9 external pages.

There is no https://www.treatwell.it/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.treatwell.it/saloni/trattamento-colore-uomo,taglio-barba,taglio-uomo/offerta-tipo-locale/in-italia and https://www.treatwell.it/saloni/award-top-rated-2026/offerta-tipo-locale/%7B%7BlocationOrPostalRef%7D%7D are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.treatwell.it/saloni/trattamento-gruppo-capelli/in-italia and https://www.treatwell.it/saloni/trattamento-colore-uomo,taglio-barba,taglio-uomo/offerta-tipo-locale/in-italia all use the title “Top 20 Parrucchieri a Italia - Treatwell”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.treatwell.it/inspiration/showcasing-the-app-ss19 has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.treatwell.it/saloni/trattamento-gruppo-capelli/in-italia and https://www.treatwell.it/saloni/trattamento-colore-uomo,taglio-barba,taglio-uomo/offerta-tipo-locale/in-italia use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.treatwell.it/saloni/trattamento-gruppo-capelli/in-italia, whose canonical is https://www.treatwell.it/saloni/trattamento-gruppo-capelli/offerta-tipo-locale/in-italia. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.treatwell.it/inspiration/showcasing-the-app-ss19 has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.treatwell.it/inspiration/showcasing-the-app-ss19 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

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