omasindustries.com website review

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

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

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

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

Your mobile performance score is 53 (desktop: 36). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.5 MB and 758 ms of main-thread time.

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

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

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

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

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

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.

3 KiB could be saved by minifying JavaScript.

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 7.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 105.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The innovation whirlwind”.

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

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

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

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

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

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

Your homepage downloads 24.9 MB in 71 requests on a phone: images 22.5 MB (12), scripts 1.7 MB (27) and other files 441 KiB (19). Under 2 MB keeps phones on slow connections fast.

8 images weigh 16.6 MB together. On a phone connection a single image that size takes seconds.

9 images are downloaded at several times the size a phone draws them, for example [email protected] at 1,820 px wide, shown at 350 px. Resized copies would save about 11.5 MB.

9 images (17.1 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.

9 images further down the page (17.1 MB) 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 7.06 g of CO₂e: 847.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

Some list items are not inside a list.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 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. (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 111 pages on omasindustries.com and 5 external pages.

The HTML your server sends has 421 of the 750 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://omasindustries.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://omasindustries.com/it/case-history, https://omasindustries.com/it/news-eventi, https://omasindustries.com/it/omix-division, https://omasindustries.com/it/omas-steel-division, https://omasindustries.com/it/assistenza and https://omasindustries.com/it/dove-siamo and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://omasindustries.com/it/omix-division, https://omasindustries.com/it/omas-steel-division, https://omasindustries.com/it/dove-siamo, https://omasindustries.com/it/richiedi-informazioni, https://omasindustries.com/it/lavorare-in-omas and https://omasindustries.com/it/la-nostra-storia have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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.

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

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

Before a visitor clicks anything, the page loads Google Ads 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 4 cookies (measured from a US location before any click).

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