netinsurance.it website review

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

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

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

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

3 images could be 192 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

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

About 315 KiB of JavaScript is downloaded but never used on this page.

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

4 third-party services load with your homepage (Google CDN, Cloudflare CDN and Other Google APIs/SDKs and others), adding 416 KiB and 120 ms of main-thread time.

1 long task block the main thread while loading, the longest for 124 ms. During a long task the page ignores taps.

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.

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

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

Your largest element takes 6.7 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 (6.3 s).

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

The first text or image appears after 3.2 s on a phone. Good is under 1.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.6 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 2.5 MB in 56 requests on a phone: images 1.2 MB (19), scripts 542 KiB (16) and media 472 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 27001_SG_SSI_sg05.jpg at 709 px wide, shown at 150 px. Resized copies would save about 108 KiB.

2 images (269 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.

1 image further down the page (181 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails 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.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 13 characters: “Net Insurance”. Between 30 and 65 characters leaves room to say what you do and for whom.

No XML sitemap at http://www.netinsurance.it/sitemap_index.xml, so Google discovers your pages only by following links.

The homepage links to 70 pages on netinsurance.it and 11 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.netinsurance.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.netinsurance.it/il-gruppo/net-insurance and https://www.netinsurance.it/il-gruppo/net-insurance-life all use the title “Dati societari – Net Insurance”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.netinsurance.it/parita-di-genere, https://www.netinsurance.it/principi-di-sicurezza-delle-informazioni, https://www.netinsurance.it/comunicazione/sponsorizzazioni and https://www.netinsurance.it/distributore/banche have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.netinsurance.it/sostenibilita and https://www.netinsurance.it/politica-di-impegno use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.netinsurance.it/il-gruppo/net-insurance, whose canonical is https://www.netinsurance.it/il-gruppo/net-insurance/dati-societari. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.netinsurance.it/il-gruppo/vision-mission-valori has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.netinsurance.it/il-gruppo/net-insurance, https://www.netinsurance.it/il-gruppo/net-insurance-life, https://www.netinsurance.it/parita-di-genere, https://www.netinsurance.it/sostenibilita, https://www.netinsurance.it/comunicazione/sponsorizzazioni and https://www.netinsurance.it/distributore/banche took over 3 s to send their HTML from our server.

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

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

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

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.

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

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