leoncinisoftware.it website review

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

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

10 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

YouTube costs a phone 459 ms of main-thread work and 979 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 548 KiB of JavaScript is downloaded but never used on this page.

6 KiB could be saved by minifying CSS.

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

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

12 KiB could be saved by minifying JavaScript.

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 page becomes fully interactive after 17.8 s. Good is under 3.8 s.

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HAI UN SITO INTERNET VECCHIO? TE LO RIFACCIAMO GRATIS!”.

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

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

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

01.png weighs 576 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.7 MB in 79 requests on a phone: images 2.3 MB (23), scripts 1.0 MB (27) and fonts 150 KiB (4). Under 2 MB keeps phones on slow connections fast.

10 images (1.3 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.

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

2 images are downloaded at several times the size a phone draws them, for example 01.png at 1,200 px wide, shown at 234 px. Resized copies would save about 441 KiB.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

13 images have no alt text, which hurts accessibility and image search.

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

6 visible links have no text or label, so screen readers cannot say where they go.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

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

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

Your meta description is only 50 characters: “Saas Cloud Mobile Website Template - Download Now!”. 70 to 160 characters is enough to sell the click.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

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://leoncinisoftware.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://leoncinisoftware.it/0-9.htm, https://leoncinisoftware.it/0-11.htm and https://leoncinisoftware.it/0-17.htm have no <title>, so Google invents the link text in results.

https://leoncinisoftware.it/0-9.htm, https://leoncinisoftware.it/0-11.htm, https://leoncinisoftware.it/0-17.htm and https://leoncinisoftware.it/pac.htm have no meta description, so Google writes the search snippet from whatever text it finds.

https://leoncinisoftware.it/0-9.htm, https://leoncinisoftware.it/0-11.htm and https://leoncinisoftware.it/0-17.htm have no <h1> headline, so visitors and search engines get no clear main topic.

https://leoncinisoftware.it/0-17.htm and https://leoncinisoftware.it/pac.htm have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://leoncinisoftware.it/0-9.htm took over 3 s to send its HTML from our server.

We fetched 4 pages linked from your homepage and read each the way a search engine does.

6 images failed to load on a phone, for example http://leoncinisoftware.it/gofarma.gif.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

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 404 (Not Found)”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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.

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 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 1 cookie, 1 of them by other companies (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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.