Website review, no card needed
unoaerre.it website review
Visit site (opens in a new tab)Reviewed 22 October 202636 issues · 90 checks
This review found 36 issues worth fixing on unoaerre.it, 13 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79C- #56,210 of 126,199 reviewed websitesbeats 50%
- #36,672 of 70,392 online storesbeats 42%
- #144 of 730 Magento storesbeats 76%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 170 ms |
| May 9, 2026 | 169 ms |
| May 16, 2026 | 161 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 131 ms |
| Jun 13, 2026 | 130 ms |
| Jun 20, 2026 | 133 ms |
| Jun 27, 2026 | 132 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 132 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 136 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 144 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Reduce unused JavaScript
1.8 s · 452 KiBAbout 452 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,253 HTML elements
The page has 5,253 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, iubenda and Vimeo and others), adding 9.2 MB and 855 ms of main-thread time.
Improve image delivery
750 ms · 333 KiB7 images could be 333 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Vimeo adds 114 ms
114 msVimeo costs a phone 114 ms of main-thread work and 8.6 MB 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.
Google Tag Manager adds 579 ms
579 msGoogle Tag Manager costs a phone 579 ms of main-thread work and 523 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.
Render-blocking requests
450 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 417 ms. During a long task the page ignores taps.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
300 ms · 61 KiB9 files are served with short cache lifetimes, so returning visitors download them again (61 KiB).
Reduce unused CSS
170 ms · 59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 64 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 109 ms
109 msYour server sent the HTML in 109 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.6 s
10.6 sYour largest element takes 10.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nuova Stagione, Nuovi Gioielli”.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Time to Interactive: 11.3 s
11.3 sThe page becomes fully interactive after 11.3 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 156 ms
156 msReal visitors wait 156 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 555 ms
555 msReal visitors wait 555 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 170 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.0 MB in 63 requests
10.0 MBYour homepage downloads 10.0 MB in 63 requests on a phone: other files 8.2 MB (16), scripts 1.0 MB (16) and images 571 KiB (19). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
76 KiB2 images are downloaded at several times the size a phone draws them, for example Boule_banner_homepage_mobile_v2_1920x1200.jpg at 1,440 px wide, shown at 390 px. Resized copies would save about 76 KiB.
3 images below the first screen load straight away
3 images further down the page (295 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (136 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.
About 2.8 g of CO₂ per visit
2.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.84 g of CO₂e: 341.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “UNOAERRE | Italian-made jewelry since 1926 | New Collections | UNOAERRE Gioielli”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
384 internal links, 13 external
The homepage links to 384 pages on unoaerre.it and 13 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Scopri i Gioielli Unoaerre. Fedi nuziali, Bracciali, Collane, Orecchini. Le nuove collezioni sono online sul sul sito u…”.
One H1 headline
Your main headline reads: “Nuova Stagione, Nuovi Gioielli”.
Canonical URL set
The canonical URL is https://www.unoaerre.it/it/.
Structured data in place
Structured data found: Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.unoaerre.it/sitemaps/it/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.unoaerre.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.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,071 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages share a title
https://www.unoaerre.it/it/anelli/scelti-per-te/novita-unoaerre, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-chicco, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-punti-luce, https://www.unoaerre.it/it/anelli/argento, https://www.unoaerre.it/it/anelli/fashion and https://www.unoaerre.it/it/bracciali and 5 others all use the title “Client Challenge”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://www.unoaerre.it/it/anelli/scelti-per-te/novita-unoaerre, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-chicco, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-punti-luce, https://www.unoaerre.it/it/anelli/argento, https://www.unoaerre.it/it/anelli/fashion and https://www.unoaerre.it/it/bracciali and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://www.unoaerre.it/it/anelli/scelti-per-te/novita-unoaerre, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-chicco, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-punti-luce, https://www.unoaerre.it/it/anelli/argento, https://www.unoaerre.it/it/anelli/fashion and https://www.unoaerre.it/it/bracciali and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages with very little text
https://www.unoaerre.it/it/anelli/scelti-per-te/novita-unoaerre, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-chicco, https://www.unoaerre.it/it/anelli/scelti-per-te/anelli-punti-luce, https://www.unoaerre.it/it/anelli/argento, https://www.unoaerre.it/it/anelli/fashion and https://www.unoaerre.it/it/bracciali and 5 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 158 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
16 of 19 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 441 words of copy
The homepage carries about 441 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “brands/whatsapp Whatsapp e-shop”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at unoaerre.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Magento
- Analytics
- Google Tag Manager
Company
- Founded
- 1926
- Headquarters
- Arezzo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on unoaerre.it, including 17 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.