Website review, no card needed

antonymorato.com logo

antonymorato.com website review

Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 85 checks

This review found 41 issues worth fixing on antonymorato.com, 18 of them high impact, across 85 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
4.1 s3.2 sMay 9Oct 244.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.6 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.7 s
Sep 5, 20263.7 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.0 s
Oct 17, 20264.0 s
Oct 24, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
873 ms707 msMay 9Oct 24726 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026835 ms
May 16, 2026838 ms
May 23, 2026838 ms
May 30, 2026838 ms
Jun 6, 2026854 ms
Jun 13, 2026840 ms
Jun 20, 2026829 ms
Jun 27, 2026828 ms
Jul 4, 2026827 ms
Jul 11, 2026838 ms
Jul 18, 2026838 ms
Jul 25, 2026815 ms
Aug 1, 2026808 ms
Aug 8, 2026790 ms
Aug 15, 2026780 ms
Aug 22, 2026790 ms
Aug 29, 2026780 ms
Sep 5, 2026781 ms
Sep 12, 2026771 ms
Sep 19, 2026760 ms
Sep 26, 2026752 ms
Oct 3, 2026732 ms
Oct 10, 2026727 ms
Oct 17, 2026726 ms
Oct 24, 2026726 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 antonymorato.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. antonymorato.com at 0.7 s0.7 s
  2. antonymorato.com at 1.4 s1.4 s
  3. antonymorato.com at 2.1 s2.1 s
  4. antonymorato.com at 2.8 s2.8 s
  5. antonymorato.com at 3.5 s3.5 s
  6. antonymorato.com at 4.2 s4.2 s
  7. antonymorato.com at 4.9 s4.9 s
  8. antonymorato.com at 5.6 s5.6 s

Speed

14 to fix8
  • Use efficient cache lifetimes

    1.2 s · 14.8 MB

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

  • Reduce unused JavaScript

    7.4 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.4 s faster on a phone.

  • Main-thread work: 10.8 s

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

  • Mobile performance score: 8

    8/100

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

  • 3,324 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (filoblu.com, Google CDN and ZenDesk and others), adding 21.7 MB and 1.9 s of main-thread time.

  • filoblu.com adds 679 ms

    679 ms

    filoblu.com costs a phone 679 ms of main-thread work and 19.4 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.

  • Improve image delivery

    600 ms · 2.0 MB

    23 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Google CDN adds 404 ms

    404 ms

    Google CDN costs a phone 404 ms of main-thread work and 733 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.

  • Font display

    400 ms

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

  • ZenDesk adds 235 ms

    235 ms

    ZenDesk costs a phone 235 ms of main-thread work and 391 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.

  • addsauce.com adds 204 ms

    204 ms

    addsauce.com costs a phone 204 ms of main-thread work and 553 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.

  • userway.org adds 93 ms

    93 ms

    userway.org costs a phone 93 ms of main-thread work and 442 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

    150 ms · 112 KiB

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

  • Legacy JavaScript

    150 ms · 13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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: 140 ms

    140 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Real-user INP: 582 ms

    582 ms

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

  • Real-user CLS: 2.00

    2.00

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

  • Cumulative Layout Shift: 2.218

    2.218

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

  • Largest Contentful Paint: 31.5 s

    31.5 s

    Your largest element takes 31.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We (Antony Morato) and selected third parties (27) collect …”.

  • Time to Interactive: 38.2 s

    38.2 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 38 images without width and height

    38 images have no width and height attributes, so the layout jumps as each one loads.

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

    +17%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 743 ms

    743 ms

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

Images and page weight

2 to fix60
  • Page weight: 24.8 MB in 302 requests

    24.8 MB

    Your homepage downloads 24.8 MB in 302 requests on a phone: media 16.7 MB (7), images 3.8 MB (46) and scripts 2.9 MB (50). Under 2 MB keeps phones on slow connections fast.

  • 20 images far larger than shown

    358 KiB

    20 images are downloaded at several times the size a phone draws them, for example FW26SHOPBY213.jpg at 960 px wide, shown at 300 px. Resized copies would save about 358 KiB.

  • About 7.0 g of CO₂ per visit

    7.04 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 58 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, 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.

  • 10 internal links, 1 external

    The homepage links to 10 pages on antonymorato.com and 1 external page.

7 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Visit the Official Antony Morato Online Shop ⋆ Casual but refined Men's Clothing, Shoes and Accessories ⋆ Discover the …”.

  • One H1 headline

    Your main headline reads: “Antony Morato - Official Online Shop”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Antony Morato ⋆ Official Website and Online Shop”.

  • Canonical URL set

    The canonical URL is https://www.antonymorato.com/us/.

  • 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.antonymorato.com/media/sitemap/it/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    10%

    A phone browser shows 1,073 words, but the HTML your server sends has only 109. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.antonymorato.com/us/lookbook-kids is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.antonymorato.com/us/lookbook-kids has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.antonymorato.com/us/lookbook-kids and https://www.antonymorato.com/us/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.antonymorato.com/us/shop-by-look.html has 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.

  • 9 internal pages checked

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

4 checks passed
  • Linked pages load

    All 9 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.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 13 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are 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 “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

  • 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 1,073 words of copy

    The homepage carries about 1,073 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

    The homepage has 2 calls to action, for example “SHOP BY LOOK” and “Sign up now”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 11 cookies set on arrival

    11

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

  • 22 other companies contacted

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

2 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on antonymorato.com, including 24 speed issues, 1 SEO issue and 2 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
antonymorato.com website review: scores and fixes