ranocchi.it website review

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

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

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

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

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

143 KiB could be saved by minifying CSS.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

18 KiB could be saved by minifying JavaScript.

1 long task block the main thread while loading, the longest for 124 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.

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

Your largest element takes 17.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

1 image 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.

Your homepage downloads 3.1 MB in 62 requests on a phone: images 1.7 MB (22), scripts 707 KiB (27) and stylesheets 552 KiB (11). Under 2 MB keeps phones on slow connections fast.

12 images (671 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.

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

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

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

6 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.

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

Your title is 66 characters, so Google will cut it off around 60: “Software gestionali Commercialisti, Consulenti del Lavoro, Aziende”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

4 links have no real href, so search engines can't follow them.

The homepage links to 219 pages on ranocchi.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://ranocchi.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.

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

19 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.