Website review, no card needed

alducadaosta.com logo

alducadaosta.com website review

Visit site (opens in a new tab)Reviewed 18 October 202635 issues · 75 checks

This review found 35 issues worth fixing on alducadaosta.com, 18 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.5 sApr 25Oct 102.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.7 s
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20262.1 s
Jun 6, 20262.4 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.4 s
Jul 4, 20262.0 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
111 ms88 msApr 25Oct 10108 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202692 ms
May 2, 202691 ms
May 9, 202694 ms
May 16, 202694 ms
May 23, 202696 ms
May 30, 202699 ms
Jun 6, 2026102 ms
Jun 13, 2026104 ms
Jun 20, 2026105 ms
Jun 27, 2026104 ms
Jul 4, 2026103 ms
Jul 11, 2026102 ms
Jul 18, 2026104 ms
Jul 25, 2026103 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026105 ms
Aug 22, 2026107 ms
Aug 29, 2026106 ms
Sep 5, 2026106 ms
Sep 12, 2026103 ms
Sep 19, 2026103 ms
Sep 26, 2026106 ms
Oct 3, 2026105 ms
Oct 10, 2026108 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

Full-page screenshot of alducadaosta.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alducadaosta.com at 0.6 s0.6 s
  2. alducadaosta.com at 1.2 s1.2 s
  3. alducadaosta.com at 1.7 s1.7 s
  4. alducadaosta.com at 2.3 s2.3 s
  5. alducadaosta.com at 2.9 s2.9 s
  6. alducadaosta.com at 3.5 s3.5 s
  7. alducadaosta.com at 4.0 s4.0 s
  8. alducadaosta.com at 4.6 s4.6 s

Speed

9 to fix33
  • Use efficient cache lifetimes

    26.9 s · 5.3 MB

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

  • Improve image delivery

    17.6 s · 3.3 MB

    2 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.6 s faster on a phone.

  • Reduce unused JavaScript

    2.3 s · 428 KiB

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

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Clerk.io ApS and others), adding 6.1 MB and 910 ms of main-thread time.

  • Azure Web Services adds 52 ms

    52 ms

    Azure Web Services costs a phone 52 ms of main-thread work and 5.2 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 471 ms

    471 ms

    Google Tag Manager costs a phone 471 ms of main-thread work and 539 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.

  • 2,729 HTML elements

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

  • Main-thread work: 2.1 s

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

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    47 KiB

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

  • Legacy JavaScript

    27 KiB

    Polyfills for old browsers add 27 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: 86 ms

    86 ms

    Your server sent the HTML in 86 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 36.3 s

    36.3 s

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

  • Time to Interactive: 36.3 s

    36.3 s

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

  • Cumulative Layout Shift: 1.014

    1.014

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Real-user TTFB: 883 ms

    883 ms

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

  • Total Blocking Time: 468 ms

    468 ms

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

  • Tap response (INP) got 16% slower for real visitors

    +16%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix33
  • Page weight: 6.4 MB in 78 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 78 requests on a phone: images 5.1 MB (20), scripts 1.0 MB (21) and other files 205 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.80 g

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

Accessibility

8 to fixGoogle 8245
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Zoom is disabled

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 16 tap targets too small

    16 tap targets are too small or too close together to hit reliably with a finger.

  • 7 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 2 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 6 WCAG 2.2 A/AA and best-practice rules on the phone render: 2 passed and 4 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10087
  • No H1 headline

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

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 387 internal links, 7 external

    The homepage links to 387 pages on alducadaosta.com and 7 external pages.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Lo Shop Online Al Duca D'Aosta seleziona per te i top fashion designer: acquista capi firmati e di lusso e crea un look…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Al Duca d’Aosta Negozio Online: Moda di Lusso Donna e Uomo”.

  • Canonical URL set

    The canonical URL is https://www.alducadaosta.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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.alducadaosta.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.alducadaosta.com/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.

2 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, logo, description and contact details; sameAs (social profiles) would complete it.

Other pages

3 to fix75
  • 1 page without a title

    https://www.alducadaosta.com/it/donna/designers has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.alducadaosta.com/it/donna/designers has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.alducadaosta.com/it/donna and https://www.alducadaosta.com/it/donna/designers have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.alducadaosta.com/it/donna/outlet, https://www.alducadaosta.com/it/donna/abbigliamento, https://www.alducadaosta.com/it/donna/abbigliamento/abiti, https://www.alducadaosta.com/it/donna/abbigliamento/camicie, https://www.alducadaosta.com/it/donna/abbigliamento/giacche and https://www.alducadaosta.com/it/donna/abbigliamento/intimo and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 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.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    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 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • No direct contact details

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

  • Only about 2 words

    The homepage has only about 2 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Insta Shop” and “Contact us”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • No consent tool detected

    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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 alducadaosta.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on alducadaosta.com, including 16 speed issues, 2 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25