Website review, no card needed

antonia.it logo

antonia.it website review

Visit site (opens in a new tab)Reviewed 24 October 202635 issues · 86 checks

This review found 35 issues worth fixing on antonia.it, 13 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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.6 s2.3 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
134 ms109 msMay 2Oct 17120 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026120 ms
May 9, 2026121 ms
May 16, 2026120 ms
May 23, 2026118 ms
May 30, 2026118 ms
Jun 6, 2026119 ms
Jun 13, 2026120 ms
Jun 20, 2026120 ms
Jun 27, 2026121 ms
Jul 4, 2026121 ms
Jul 11, 2026128 ms
Jul 18, 2026131 ms
Jul 25, 2026129 ms
Aug 1, 2026127 ms
Aug 8, 2026121 ms
Aug 15, 2026118 ms
Aug 22, 2026114 ms
Aug 29, 2026113 ms
Sep 5, 2026113 ms
Sep 12, 2026115 ms
Sep 19, 2026112 ms
Sep 26, 2026114 ms
Oct 3, 2026116 ms
Oct 10, 2026116 ms
Oct 17, 2026120 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 antonia.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. antonia.it at 0.7 s0.7 s
  2. antonia.it at 1.3 s1.3 s
  3. antonia.it at 1.9 s1.9 s
  4. antonia.it at 2.6 s2.6 s
  5. antonia.it at 3.3 s3.3 s
  6. antonia.it at 3.9 s3.9 s
  7. antonia.it at 4.6 s4.6 s
  8. antonia.it at 5.2 s5.2 s

Speed

11 to fix54
  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 4.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (iubenda, Google CDN and Klaviyo and others), adding 1.7 MB and 1.4 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 922 KiB

    About 922 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Improve image delivery

    650 ms · 555 KiB

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

  • Mobile performance score: 54

    54/100

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

  • iubenda adds 748 ms

    748 ms

    iubenda costs a phone 748 ms of main-thread work and 129 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.

  • Reduce unused CSS

    300 ms · 120 KiB

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

  • Google CDN adds 250 ms

    250 ms

    Google CDN costs a phone 250 ms of main-thread work and 731 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,337 HTML elements

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

  • Klaviyo adds 151 ms

    151 ms

    Klaviyo costs a phone 151 ms of main-thread work and 345 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.

  • Use efficient cache lifetimes

    150 ms · 218 KiB

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

  • 14 long tasks on the main thread

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

  • Minify CSS

    29 KiB

    29 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 81 ms

    81 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 25.3 s

    25.3 s

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

  • Largest Contentful Paint: 8.2 s

    8.2 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Cumulative Layout Shift: 0.153

    0.153

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

7 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: 2.4 s

    2.4 s

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

  • Real-user INP: 119 ms

    119 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 585 ms

    585 ms

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

  • Total Blocking Time: 168 ms

    168 ms

    Scripts block the page for only 168 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix64
  • Page weight: 5.9 MB in 309 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 309 requests on a phone: scripts 2.2 MB (106), images 1.9 MB (24) and other files 1.5 MB (160). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    7FAM_BANNER_MOBILE_e430cf13-b9b4-4351-b782-4d9004646906.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 in older formats

    1 image (127 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 1.7 g of CO₂ per visit

    1.67 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 7789
  • 1 button without a name

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (3 elements)

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

  • Zoom is disabled

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

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

  • 21 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 43 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 10086
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Antonia Milano | Exclusive clothing for men and women | Online store”.

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.antonia.it/cdn/shop/t/95/assets/logo.png?v=70794")”.

  • No social preview image

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

  • 569 internal links, 12 external

    The homepage links to 569 pages on antonia.it and 12 external pages.

5 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Enter the Antonia world: Limited Editions, Exclusive releases, Seasonal Must-haves and Iconic pieces. Be inspired by ou…”.

  • One H1 headline

    Your main headline reads: “Antonia | Abbigliamento e Accessori - Luxury Brand”.

  • Canonical URL set

    The canonical URL is https://www.antonia.it/en-us.

  • 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.antonia.it/sitemap.xml.

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,178 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.antonia.it/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.antonia.it/en-us/blogs/sneakers has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 2 broken images

    2 images failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0708/4572/7012/files/ANTONIA_capsLogo_001_copia_4d1aa893-4b58-4b90-9562-36df912275cc.jpg?v=1713530396.

  • 85 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://stylegenie.4gift.com/v1/style.css' from origin 'https://www.antonia.it' has been b…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 411 words of copy

    The homepage carries about 411 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more and customise”.

  • 2 calls to action

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

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.

  • 16 cookies set on arrival

    16

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

  • 29 other companies contacted

    Loading the homepage contacts 29 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 antonia.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify Hosted

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 antonia.it, including 16 speed issues, 3 SEO issues and 1 conversion gap. 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