legami.com website review

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

The page has 4,059 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

4 third-party services load with your homepage (Cookiebot, Foursixty and YouTube and others), adding 357 KiB and 201 ms of main-thread time.

About 161 KiB of CSS is downloaded but never applied on this page.

6 images could be 156 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

9 files are served with short cache lifetimes, so returning visitors download them again (118 KiB).

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.

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 517 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.45 (75th percentile). Good is under 0.1.

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

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

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

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

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

Your homepage downloads 3.7 MB in 157 requests on a phone: images 2.2 MB (108), scripts 749 KiB (10) and fonts 466 KiB (8). Under 2 MB keeps phones on slow connections fast.

LEGAMI_E-COMMERCE_NATALE_HES001_MOBILE EP2.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example WXMAS0001_2.jpg at 600 px wide, shown at 160 px. Resized copies would save about 21 KiB.

1 image (78 KiB) is 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.06 g of CO₂e: 127.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 70 characters, so Google will cut it off around 60: “Legami Milano | Agende e Calendari, Cartoleria, Idee Regalo, Accessori”.

Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://legami-production.mobify-storefront.com/it-it)”.

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

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

The homepage links to 832 pages on legami.com and 7 external pages.

There is no /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.

Your homepage links to /esplora, /esplora/mondi-legami, /collezione-natale.html, /esplora/mondi-legami/extraordinary-stationery, /esplora/mondi-legami/diaries-and-calendars and /esplora/mondi-legami/partners-in-style and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.

/it-it/boutique-list, /it-it/assistenza-hubFAQ.html and /it-it/accedi have no meta description, so Google writes the search snippet from whatever text it finds.

/it-it/boutique-list, /it-it/assistenza-hubFAQ.html, /it-it/accedi and /it-it/wishlist have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

Large scripts ship without source maps.

15 links from your homepage to your own site are broken, for example https://www.legami.com/esplora (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://legami.com goes through 2 redirects before the homepage loads.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

legami.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

legami.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

legami.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,119 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 4 cookies (measured from a US location before any click).

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