Website review, no card needed

michaelkors.com logo

michaelkors.com website review

Visit site (opens in a new tab)Reviewed 12 October 202643 issues · 88 checks

This review found 43 issues worth fixing on michaelkors.com, 17 of them high impact, across 88 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.3 s2.0 sApr 18Oct 32.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20262.2 s
Apr 25, 20262.2 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
259 ms204 msApr 18Oct 3253 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026227 ms
Apr 25, 2026222 ms
May 2, 2026221 ms
May 9, 2026220 ms
May 16, 2026213 ms
May 23, 2026211 ms
May 30, 2026210 ms
Jun 6, 2026213 ms
Jun 13, 2026220 ms
Jun 20, 2026226 ms
Jun 27, 2026229 ms
Jul 4, 2026231 ms
Jul 11, 2026231 ms
Jul 18, 2026230 ms
Jul 25, 2026229 ms
Aug 1, 2026228 ms
Aug 8, 2026228 ms
Aug 15, 2026230 ms
Aug 22, 2026235 ms
Aug 29, 2026238 ms
Sep 5, 2026246 ms
Sep 12, 2026248 ms
Sep 19, 2026252 ms
Sep 26, 2026252 ms
Oct 3, 2026253 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 michaelkors.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. michaelkors.com at 1.1 s1.1 s
  2. michaelkors.com at 2.1 s2.1 s
  3. michaelkors.com at 3.1 s3.1 s
  4. michaelkors.com at 4.2 s4.2 s
  5. michaelkors.com at 5.3 s5.3 s
  6. michaelkors.com at 6.3 s6.3 s
  7. michaelkors.com at 7.4 s7.4 s
  8. michaelkors.com at 8.4 s8.4 s

Speed

16 to fix32
  • Use efficient cache lifetimes

    4.3 s · 3.1 MB

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

  • Reduce unused JavaScript

    4.3 s · 2.1 MB

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

  • Main-thread work: 14.0 s

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

  • mPulse adds 1.4 s

    1.4 s

    mPulse costs a phone 1.4 s of main-thread work and 60 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.

  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. 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 (mPulse, Google CDN and Facebook and others), adding 2.2 MB and 2.8 s of main-thread time.

  • Improve image delivery

    150 ms · 673 KiB

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

  • Legacy JavaScript

    700 ms · 110 KiB

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

  • Reduce unused CSS

    300 ms · 227 KiB

    About 227 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 302 ms

    302 ms

    Google CDN costs a phone 302 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 281 ms

    281 ms

    Facebook costs a phone 281 ms of main-thread work and 277 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.

  • ContentSquare adds 255 ms

    255 ms

    ContentSquare costs a phone 255 ms of main-thread work and 175 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,460 HTML elements

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

  • ssgocc.com adds 167 ms

    167 ms

    ssgocc.com costs a phone 167 ms of main-thread work and 347 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.

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

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

    8 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 17.6 s

    17.6 s

    Your largest element takes 17.6 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: 48.2 s

    48.2 s

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

  • Speed Index: 15.0 s

    15.0 s

    Visually, the page fills in at 15.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: 3.2 s

    3.2 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 215 ms

    215 ms

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

  • Real-user FCP: 2.1 s

    2.1 s

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

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

3 checks passed
  • 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 TTFB: 467 ms

    467 ms

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

  • Cumulative Layout Shift: 0.045

    0.045

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

Images and page weight

1 to fix33
  • Page weight: 13.6 MB in 403 requests

    13.6 MB

    Your homepage downloads 13.6 MB in 403 requests on a phone: media 6.2 MB (1), scripts 5.0 MB (162) and images 1.3 MB (76). Under 2 MB keeps phones on slow connections fast.

  • About 3.9 g of CO₂ per visit

    3.86 g

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

Accessibility

6 to fixGoogle 9250
  • 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.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

2 checks passed
  • Every image has alt text

    All 42 images 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9283
  • Title is long (101 characters)

    Your title is 101 characters, so Google will cut it off around 60: “Michael Kors USA: Designer Handbags, Clothing, Menswear, Watches, Shoes, And More | Micha…”.

  • Meta description is long (174 characters)

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

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

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

  • 88 internal links, 13 external

    The homepage links to 88 pages on michaelkors.com and 13 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Michael Kors”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Corporation and WebSite.

  • 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.michaelkors.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.michaelkors.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, sameAs (social profiles) and description; contact details would complete it.

Other pages

100
  • 15 internal pages checked

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

7 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 6 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5493
  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 660 words of visible text.

3 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “SHOP SALE”, “The Boot Shop” and “The Men's Shop”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (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.

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 michaelkors.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 43 issues on michaelkors.com, including 25 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