climando.it website review

hcaptcha.com costs a phone 1.1 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (hcaptcha.com, ZenDesk and cdn-cookieyes.com and others), adding 2.4 MB and 1.9 s of main-thread time.

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

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

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

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

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

cdn-cookieyes.com costs a phone 253 ms of main-thread work and 41 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.

Shopify costs a phone 72 ms of main-thread work and 545 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 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

4 KiB could be saved by minifying JavaScript.

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

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

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.

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

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.

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

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

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

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 4.8 MB in 383 requests on a phone: scripts 1.9 MB (103), images 1.2 MB (79) and other files 978 KiB (143). Under 2 MB keeps phones on slow connections fast.

climando-it-area-b2b-banner-homepage_34ed472c-1200-4114-a0c8 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images are downloaded at several times the size a phone draws them, for example climando-it-riconoscimento-2021_9b74540a-83d4-4e32-b055-43be at 960 px wide, shown at 150 px. Resized copies would save about 108 KiB.

4 images further down the page (229 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 dropdown has no label.

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

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

The homepage links to 603 pages on climando.it and 14 external pages.

/products/condizionatore-climatizzatore-hisense-monosplit-inverter-easy-smart-r-32-12000-btu-ca35mr0bg-wi-fi-integrato and /products/condizionatore-climatizzatore-hisense-monosplit-inverter-easy-smart-r-32-18000-btu-ca50xs1gg-wi-fi-integrato all use the title “Condizionatore Climatizzatore Hisense Monosplit Inverter Easy Smart R…”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/products/condizionatore-climatizzatore-hisense-monosplit-inverter-easy-smart-r-32-12000-btu-ca35mr0bg-wi-fi-integrato and /products/condizionatore-climatizzatore-hisense-monosplit-inverter-easy-smart-r-32-18000-btu-ca50xs1gg-wi-fi-integrato use the same meta description. A description written for each page earns more clicks.

/products/condizionatore-climatizzatore-hisense-monosplit-inverter-easy-smart-r-32-12000-btu-ca35mr0bg-wi-fi-integrato, /products/condizionatore-climatizzatore-hisense-dual-split-inverter-r-32-hi-comfort-900012000-btu-con-2amw42u4rgc-wifi-integrato-912, /products/condizionatore-climatizzatore-hisense-dual-split-inverter-r-32-hi-comfort-90009000-btu-con-2amw35u4rgc-wifi-integrato-99, /products/condizionatore-climatizzatore-hisense-monosplit-inverter-easy-smart-r-32-18000-btu-ca50xs1gg-wi-fi-integrato, /products/recuperatore-di-calore-puntuale-ideal-clima-modello-kers-50-vrks52w-con-telecomando-funzione-antimuffa-wi-fi-optional and /products/caldaia-a-condensazione-ferroli-bluehelix-theta-24c-completa-di-kit-scarico-fumi-metanogpl-cod-0tpy2awa and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 2 deprecated browser APIs 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 “Uncaught SyntaxError: Identifier 'FeedatyWidget' has already been declared”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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 longest form asks for 28 fields (0 required). Every extra field lowers completion.

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 1,633 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 6 cookies (measured from a US location before any click).

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