Website review, no card needed

ambrogioshoes.com logo

ambrogioshoes.com website review

Visit site (opens in a new tab)Reviewed 12 November 202635 issues · 87 checks

This review found 35 issues worth fixing on ambrogioshoes.com, 12 of them high impact, across 87 checks. The most urgent: shopify adds 2.1 s. 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.8 s2.0 sMay 23Nov 72.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Nov 7, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
929 ms105 msMay 23Nov 7200 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026512 ms
May 30, 2026495 ms
Jun 6, 2026545 ms
Jun 13, 2026538 ms
Jun 20, 2026490 ms
Jun 27, 2026623 ms
Jul 4, 2026619 ms
Jul 11, 2026727 ms
Jul 18, 2026751 ms
Jul 25, 2026685 ms
Aug 1, 2026670 ms
Aug 8, 2026663 ms
Aug 15, 2026775 ms
Aug 22, 2026789 ms
Aug 29, 2026834 ms
Sep 5, 2026788 ms
Sep 12, 2026724 ms
Sep 19, 2026598 ms
Sep 26, 2026387 ms
Oct 3, 2026317 ms
Oct 10, 2026250 ms
Oct 17, 2026205 ms
Oct 24, 2026209 ms
Oct 31, 2026204 ms
Nov 7, 2026200 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 ambrogioshoes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ambrogioshoes.com at 1.5 s1.5 s
  2. ambrogioshoes.com at 3.1 s3.1 s
  3. ambrogioshoes.com at 4.6 s4.6 s
  4. ambrogioshoes.com at 6.1 s6.1 s
  5. ambrogioshoes.com at 7.6 s7.6 s
  6. ambrogioshoes.com at 9.2 s9.2 s
  7. ambrogioshoes.com at 10.7 s10.7 s
  8. ambrogioshoes.com at 12.2 s12.2 s

Speed

11 to fix34
  • Shopify adds 2.1 s

    2.1 s

    Shopify costs a phone 2.1 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 18.0 s

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

  • Reduce unused JavaScript

    1.1 s · 654 KiB

    About 654 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.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 34

    34/100

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

  • 6,946 HTML elements

    The page has 6,946 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 (Shopify, Klaviyo and smile.io and others), adding 2.2 MB and 2.5 s of main-thread time.

  • Reduce unused CSS

    600 ms · 152 KiB

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

  • Improve image delivery

    100 ms · 554 KiB

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

  • 20 long tasks on the main thread

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

  • Klaviyo adds 284 ms

    284 ms

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

  • Legacy JavaScript

    200 ms · 45 KiB

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

  • Use efficient cache lifetimes

    100 ms · 89 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 30 ms

    30 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (5.6 s).

  • Speed Index: 17.8 s

    17.8 s

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

  • Time to Interactive: 21.6 s

    21.6 s

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

  • Total Blocking Time: 930 ms

    930 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Cumulative Layout Shift: 0.146

    0.146

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

  • 1 image without width and height

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

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

    2.1 s

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

  • Real-user INP: 197 ms

    197 ms

    Real visitors wait 197 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.5 s

    1.5 s

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

  • Real-user TTFB: 542 ms

    542 ms

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

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

    -60%

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

Images and page weight

1 to fix70
  • Page weight: 4.3 MB in 458 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 458 requests on a phone: scripts 2.0 MB (214), images 1.3 MB (37) and other files 358 KiB (167). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.22 g

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

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

  • Images are sized for phones

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

Accessibility

2 to fix87
  • 6 text elements with low contrast

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

  • 3 tap targets too small

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed
  • Every image has alt text

    All 128 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 8581
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Luxury Men's Shoes & Designer Handmade Footwear | AmbrogioShoes.com”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

  • Meta description is long (215 characters)

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

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 333 internal links, 3 external

    The homepage links to 333 pages on ambrogioshoes.com and 3 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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.ambrogioshoes.com/sitemap.xml.

AI search readiness

100
  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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: 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,540 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.ambrogioshoes.com/collections/mens-designer-shoes, https://www.ambrogioshoes.com/collections/mens-store, https://www.ambrogioshoes.com/collections/mens-designer-boots, https://www.ambrogioshoes.com/collections/mens-exotic-skin-shoes, https://www.ambrogioshoes.com/collections/mens-formal-shoes and https://www.ambrogioshoes.com/collections/mens-loafers and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.ambrogioshoes.com/collections/mens-designer-shoes, https://www.ambrogioshoes.com/collections/mens-designer-boots, https://www.ambrogioshoes.com/collections/mens-exotic-skin-shoes, https://www.ambrogioshoes.com/collections/mens-formal-shoes, https://www.ambrogioshoes.com/collections/mens-loafers and https://www.ambrogioshoes.com/collections/mens-moccasins 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 109 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 7785
  • 15 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Failed to construct 'URL': Invalid URL”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP ELIGIBLE STYLES & SIZES” and “LEARN MORE”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop Shoes By Style”, “Shop By Size” and “SHOP ALL ACCESSORIES”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).

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

  • 31 other companies contacted

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

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

Apps on your store

Your storefront loads 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Returngo Returns Exchanges · Smart Seo · Klip Coupons · Judge Me Reviews · Aris Product Options · Dakaas Fraud Filter · W3 Custom Order Status · Managed Markets · Inbox · Instafeed · Klaviyo Email Marketing Sms · Army Man For Stores · Essential Icon Badge Banners · Insurance Order Links 2026 · w3apps.co · amazonaws.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Cloudflare

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 ambrogioshoes.com, including 18 speed issues, 4 SEO issues and 5 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