metalco.it website review

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

5 third-party services load with your homepage (Google Tag Manager, iubenda and cloudfront.net and others), adding 10.6 MB and 655 ms of main-thread time.

cloudfront.net costs a phone 72 ms of main-thread work and 10.2 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 77 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

1 image could be 242 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

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.

Real visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “La collezione Animal Factory, disegnata da Luca Boscardin e…”. Most of its time is element render delay (4.0 s).

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

Your homepage downloads 10.7 MB in 36 requests on a phone: media 9.6 MB (1), scripts 682 KiB (22) and images 286 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

Your title is 81 characters, so Google will cut it off around 60: “Arredo Urbano: Panchine, Pensiline, Fioriere, Cestini Per Spazi Pubblici| Metalco”.

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

The homepage links to 41 pages on metalco.it and 8 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.

There is no https://www.metalco.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.metalco.it/category/metalco is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.metalco.it/metalco/chiusura-aziendale-estiva, https://www.metalco.it/category/metalco and https://www.metalco.it/metalco/metalco-sostiene-la-prevenzione-del-tumore-al-seno-insieme-a-welfarecare have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.metalco.it/contatti has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.metalco.it/applicazioni 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.

https://www.metalco.it/progetti, https://www.metalco.it/news and https://www.metalco.it/about/usiamo-materiali-riciclabili-che-durano-nel-tempo-e-rispettano-lambiente took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 374 words of visible text.

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

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

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