rhiag.com website review

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

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

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

10 images could be 874 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

About 250 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

7 third-party services load with your homepage (Google CDN, Google Maps and Optanon and others), adding 1.2 MB and 745 ms of main-thread time.

123 KiB could be saved by minifying JavaScript.

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

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

43 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (7.2 s).

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

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

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

Real visitors wait 3.0 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.

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

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

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

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

Your homepage downloads 3.5 MB in 75 requests on a phone: scripts 1.5 MB (28), images 1.2 MB (21) and other files 399 KiB (12). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example team-RH-AZ-AC.jpg at 800 px wide, shown at 168 px. Resized copies would save about 276 KiB.

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

4 images (456 KiB) 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.

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

Some list items are not inside a list.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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

8 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 only 5 characters: “Rhiag”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 29 <h1> headlines (“Automotive”, “Carrozzeria” and “Veicoli Industriali e Commerciali”). One clear main headline is easier for people and search engines.

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

There is no robots.txt at rhiag.com/robots.txt, the first file search crawlers ask for.

The homepage links to 182 pages on rhiag.com and 3 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.rhiag.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.rhiag.com/rhiag, https://www.rhiag.com/en/rhiag, https://www.rhiag.com/gamma, https://www.rhiag.com/gamma/automotive, https://www.rhiag.com/gamma/automotive/meccanica and https://www.rhiag.com/gamma/automotive/meccanica/impianto-frenante and 10 others all use the title “Rhiag”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rhiag.com/gamma/automotive/meccanica, https://www.rhiag.com/gamma/automotive/meccanica/frizione, https://www.rhiag.com/gamma/automotive/meccanica/impianti-di-scarico, https://www.rhiag.com/gamma/automotive/sistemi-termici, https://www.rhiag.com/gamma/automotive/sistemi-termici/climatizzazione and https://www.rhiag.com/gamma/automotive/sistemi-termici/termico-motore and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.rhiag.com/gamma, https://www.rhiag.com/gamma/automotive, https://www.rhiag.com/gamma/automotive/meccanica and https://www.rhiag.com/gamma/automotive/meccanica/distribuzione took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 145 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: the server responded with a status of 429 ()”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 197 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 1 cookie (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.