misterlavaggio.com website review

104 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and TikTok and others), adding 1.8 MB and 2.6 s of main-thread time.

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

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

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

TikTok costs a phone 627 ms of main-thread work and 300 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.

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

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

Facebook costs a phone 372 ms of main-thread work and 278 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.

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

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

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

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

7 KiB could be saved by minifying JavaScript.

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.

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 30.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Il lavaggio auto direttamente a casa tua Un servizio profes…”.

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

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

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

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

Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Real visitors see the first content after 2.6 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.

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

Your homepage downloads 5.1 MB in 151 requests on a phone: scripts 2.1 MB (67), images 1.9 MB (10) and fonts 423 KiB (9). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA commands must have an accessible name: 12 elements on the page fail this check, rated serious by axe-core.

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

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

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 2 <h1> headlines (“Il lavaggio autodirettamente a casa tua” and “La nostra mission”). One clear main headline is easier for people and search engines.

The homepage links to 22 pages on misterlavaggio.com and 10 external pages.

There is no https://www.misterlavaggio.com/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.misterlavaggio.com/prenota-ora and https://www.misterlavaggio.com/app all use the title “Prenota un lavaggio auto a domicilio”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.misterlavaggio.com/prenota-ora and https://www.misterlavaggio.com/app 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.misterlavaggio.com/app, whose canonical is https://www.misterlavaggio.com/prenota-ora. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.misterlavaggio.com/news-mister-lavaggio has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.misterlavaggio.com/lavaggio-auto-aziende, https://www.misterlavaggio.com/avvia-la-tua-attivita-con-mister-lavaggio, https://www.misterlavaggio.com/rivoluzione-lavaggio-auto, https://www.misterlavaggio.com/servizi-di-lavaggio-auto-a-domicilio, https://www.misterlavaggio.com/prenota-ora and https://www.misterlavaggio.com/news-mister-lavaggio and 2 others took over 3 s to send their HTML from our server.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

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

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

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

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