Website review, no card needed

alexandermcqueen.com logo

alexandermcqueen.com website review

Visit site (opens in a new tab)Reviewed 19 October 202637 issues · 85 checks

This review found 37 issues worth fixing on alexandermcqueen.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
7.1 s3.9 sApr 25Oct 105.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20264.6 s
May 2, 20264.6 s
May 9, 20264.6 s
May 16, 20264.6 s
May 23, 20264.5 s
May 30, 20264.5 s
Jun 6, 20264.4 s
Jun 13, 20264.3 s
Jun 20, 20264.3 s
Jun 27, 20264.5 s
Jul 4, 20264.6 s
Jul 11, 20264.8 s
Jul 18, 20264.9 s
Jul 25, 20264.9 s
Aug 1, 20264.9 s
Aug 8, 20265.5 s
Aug 15, 20266.1 s
Aug 22, 20266.5 s
Aug 29, 20266.7 s
Sep 5, 20266.3 s
Sep 12, 20265.9 s
Sep 19, 20265.6 s
Sep 26, 20265.2 s
Oct 3, 20265.2 s
Oct 10, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
335 ms280 msApr 25Oct 10302 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026312 ms
May 2, 2026312 ms
May 9, 2026307 ms
May 16, 2026297 ms
May 23, 2026294 ms
May 30, 2026289 ms
Jun 6, 2026286 ms
Jun 13, 2026286 ms
Jun 20, 2026286 ms
Jun 27, 2026289 ms
Jul 4, 2026294 ms
Jul 11, 2026300 ms
Jul 18, 2026306 ms
Jul 25, 2026312 ms
Aug 1, 2026320 ms
Aug 8, 2026325 ms
Aug 15, 2026329 ms
Aug 22, 2026329 ms
Aug 29, 2026325 ms
Sep 5, 2026314 ms
Sep 12, 2026309 ms
Sep 19, 2026304 ms
Sep 26, 2026301 ms
Oct 3, 2026303 ms
Oct 10, 2026302 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 alexandermcqueen.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alexandermcqueen.com at 1.3 s1.3 s
  2. alexandermcqueen.com at 2.5 s2.5 s
  3. alexandermcqueen.com at 3.8 s3.8 s
  4. alexandermcqueen.com at 5.0 s5.0 s
  5. alexandermcqueen.com at 6.3 s6.3 s
  6. alexandermcqueen.com at 7.5 s7.5 s
  7. alexandermcqueen.com at 8.8 s8.8 s
  8. alexandermcqueen.com at 10.0 s10.0 s

Speed

10 to fix35
  • Use efficient cache lifetimes

    3.9 s · 1.3 MB

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

  • Reduce unused JavaScript

    3.3 s · 1.2 MB

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

  • Improve image delivery

    1.8 s · 1.5 MB

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

  • Main-thread work: 18.8 s

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

  • Google Tag Manager adds 1.7 s

    1.7 s

    Google Tag Manager costs a phone 1.7 s of main-thread work and 989 KiB 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.

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 34). 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, TikTok and Optanon and others), adding 1.8 MB and 2.7 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    600 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

  • Legacy JavaScript

    300 ms · 69 KiB

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

  • Reduce unused CSS

    84 KiB

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

  • Minify JavaScript

    43 KiB

    43 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 25 ms

    25 ms

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

Core Web Vitals

9 to fix0
  • 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 LCP: 4.8 s

    4.8 s

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 16.2 s

    16.2 s

    Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “McQueen model in AW26”.

  • Total Blocking Time: 9.0 s

    9.0 s

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

  • Time to Interactive: 35.1 s

    35.1 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • Real-user INP: 345 ms

    345 ms

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

  • Real-user CLS: 0.25

    0.25

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

  • Tap response (INP) held steady for real visitors

    -3%

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

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

    +12%

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

3 checks passed
  • Real-user TTFB: 782 ms

    782 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.039

    0.039

    The layout barely moves while loading (CLS 0.039, good is under 0.1).

Images and page weight

3 to fix45
  • Page weight: 5.9 MB in 234 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 234 requests on a phone: scripts 3.3 MB (94), images 2.3 MB (44) and other files 194 KiB (80). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    A00755QJAGL1015_F.jpg weighs 853 KiB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    400 KiB

    3 images are downloaded at several times the size a phone draws them, for example A00755QJAGL1015_F.jpg at 668 px wide, shown at 176 px. Resized copies would save about 400 KiB.

  • About 1.7 g of CO₂ per visit

    1.68 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.68 g of CO₂e: 202.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 9294
  • 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.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 2 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No XML sitemap

    No XML sitemap at https://www.alexandermcqueen.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 39 internal links, 6 external

    The homepage links to 39 pages on alexandermcqueen.com and 6 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Welcome to the official online flagship for the Alexander McQueen fashion house. Discover designer clothing and accesso…”.

  • One H1 headline

    Your main headline reads: “New Season's Arrivals”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “McQueen US | Official Online Store”.

  • Canonical URL set

    The canonical URL is https://www.alexandermcqueen.com/en-us.

  • Structured data in place

    Structured data found: NewsArticle, 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.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    39%

    The HTML your server sends has 115 of the 292 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

Other pages

3 to fix86
  • 2 pages share a title

    https://www.alexandermcqueen.com/en-us/pr/p-A00BO9WIAMM9061.html and https://www.alexandermcqueen.com/en-us/pr/p-553680WIAIG9061.html all use the title “Men's Oversized Sneaker in White/Black | McQueen US”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages share a meta description

    https://www.alexandermcqueen.com/en-us/pr/p-A00BO9WIAMM9165.html, https://www.alexandermcqueen.com/en-us/pr/p-A00BO9WIAMM9061.html, https://www.alexandermcqueen.com/en-us/pr/p-553770WIAKY9556.html, https://www.alexandermcqueen.com/en-us/pr/p-553770WIAMO9091.html, https://www.alexandermcqueen.com/en-us/pr/p-553680WIAIG9061.html and https://www.alexandermcqueen.com/en-us/pr/p-553680WIAIG1070.html use the same meta description. A description written for each page earns more clicks.

  • 8 links to non-canonical URLs

    Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.alexandermcqueen.com/en-us/pr/p-A0078YQJAGJ2025.html, whose canonical is https://www.alexandermcqueen.com/en-us/pr/wool-barathea-mini-dress-A0078YQJAGJ2025.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages slow to respond

    https://www.alexandermcqueen.com/en-us/ca/women/collections/seasonal-edit, https://www.alexandermcqueen.com/en-us/pr/p-A0078YQJAGJ2025.html, https://www.alexandermcqueen.com/en-us/pr/p-876315WIAK49224.html, https://www.alexandermcqueen.com/en-us/ca/women/shoes, https://www.alexandermcqueen.com/en-us/ca/women/ready-to-wear and https://www.alexandermcqueen.com/en-us/ca/men/ready-to-wear and 7 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 7385
  • 6 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Ignoring duplicate Content-Security-Policy directive 'worker-src'.”.

  • 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 fix70
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 292 words of copy

    The homepage carries about 292 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 NOW” and “Shop Women”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop Now”, “Request an Appointment” and “Subscribe to the Newsletter”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

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

  • 16 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 alexandermcqueen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager

Company

Founded
1992
Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on alexandermcqueen.com, including 19 speed issues, 2 SEO issues 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