micra.it website review

7 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.4 s faster on a phone.

About 517 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

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

4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Fonts and others), adding 1.3 MB and 559 ms of main-thread time.

YouTube costs a phone 548 ms of main-thread work and 962 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.

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

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

4 long tasks block the main thread while loading, the longest for 236 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).

Desktop scores 79 but mobile only 46. 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.

Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Conosciamo i processi. Costruiamo il software che li fa evo…”.

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

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

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

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

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

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

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.

legal-home.png weighs 537 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.7 MB in 32 requests on a phone: images 1.7 MB (8), scripts 874 KiB (6) and stylesheets 91 KiB (11). Under 2 MB keeps phones on slow connections fast.

4 images (1.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

5 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example photo-1573164574572-cb89e39749b4 at 1,800 px wide, shown at 324 px. Resized copies would save about 249 KiB.

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 42 pages on micra.it and 1 external page.

Your robots.txt lets ChatGPT search (OAI-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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