Website review, no card needed
mytheresa.com website review
Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 86 checks
This review found 41 issues worth fixing on mytheresa.com, 16 of them high impact, across 86 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 313 ms |
| May 16, 2026 | 312 ms |
| May 23, 2026 | 312 ms |
| May 30, 2026 | 312 ms |
| Jun 6, 2026 | 311 ms |
| Jun 13, 2026 | 306 ms |
| Jun 20, 2026 | 305 ms |
| Jun 27, 2026 | 308 ms |
| Jul 4, 2026 | 311 ms |
| Jul 11, 2026 | 313 ms |
| Jul 18, 2026 | 310 ms |
| Jul 25, 2026 | 301 ms |
| Aug 1, 2026 | 294 ms |
| Aug 8, 2026 | 287 ms |
| Aug 15, 2026 | 284 ms |
| Aug 22, 2026 | 280 ms |
| Aug 29, 2026 | 278 ms |
| Sep 5, 2026 | 275 ms |
| Sep 12, 2026 | 276 ms |
| Sep 19, 2026 | 276 ms |
| Sep 26, 2026 | 277 ms |
| Oct 3, 2026 | 279 ms |
| Oct 10, 2026 | 278 ms |
| Oct 17, 2026 | 279 ms |
| Oct 24, 2026 | 282 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
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.1 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Improve image delivery
3.1 s · 1.4 MB8 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.
Reduce unused JavaScript
2.4 s · 533 KiBAbout 533 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 30
30/100Your mobile performance score is 30 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,142 HTML elements
The page has 3,142 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.
Use efficient cache lifetimes
600 ms · 155 KiB2 files are served with short cache lifetimes, so returning visitors download them again (155 KiB).
Reduce unused CSS
500 ms · 87 KiBAbout 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 500 ms faster on a phone.
hcaptcha.com adds 307 ms
307 mshcaptcha.com costs a phone 307 ms of main-thread work and 114 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.
3 third-party services on the page
3 third-party services load with your homepage (hcaptcha.com, Monetate and Google Tag Manager), adding 176 KiB and 409 ms of main-thread time.
Legacy JavaScript
150 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Phones get a much slower page than desktops
Desktop scores 59 but mobile only 30. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 856 ms
856 msReal visitors wait 856 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.33
0.33For real visitors the layout shifts by 0.33 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 14.8 s
14.8 sYour largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Women”.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.5 s
3.5 sReal visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 865 ms
865 msReal visitors wait 865 ms for your server to start answering (75th percentile). Good is under 800 ms.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 313 ms to 282 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 99 requests
3.8 MBYour homepage downloads 3.8 MB in 99 requests on a phone: images 2.3 MB (61), scripts 1.2 MB (22) and stylesheets 126 KiB (10). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
20d6754e-fac7-4c85-8ca8-dadb1ad9468d.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).
3 images far larger than shown
30 KiB3 images are downloaded at several times the size a phone draws them, for example 4bfe2df9-e4fc-40be-abef-716a1bf7ef68.jpg at 1,198 px wide, shown at 390 px. Resized copies would save about 30 KiB.
About 1.1 g of CO₂ per visit
1.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
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.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 86 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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
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.
224 internal links, 15 external
The homepage links to 224 pages on mytheresa.com and 15 external pages.
7 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Mytheresa offers you the finest edit in luxury! Fall in love with over 200 international designer brands such as Gucci,…”.
One H1 headline
Your main headline reads: “Mytheresa – luxury fashion and designer shopping”.
Title: 37 characters
Your title is a healthy 37 characters: “Mytheresa - The Finest Edit in Luxury”.
Canonical URL set
The canonical URL is https://www.mytheresa.com/us/en.
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.mytheresa.com/sitemap.xml.
AI search readiness
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, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,882 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.mytheresa.com/llms.txt (12 KiB, 56 links), a plain-text guide to the site for AI tools.
Other pages
9 linked pages hidden from search
https://www.mytheresa.com/us/en/women/new-arrivals/current-week, https://www.mytheresa.com/us/en/women/designers, https://www.mytheresa.com/us/en/women/clothing, https://www.mytheresa.com/us/en/women/shoes, https://www.mytheresa.com/us/en/women/bags and https://www.mytheresa.com/us/en/women/accessories and 3 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
9 pages share a title
https://www.mytheresa.com/us/en/women/new-arrivals/current-week, https://www.mytheresa.com/us/en/women/designers, https://www.mytheresa.com/us/en/women/clothing, https://www.mytheresa.com/us/en/women/shoes, https://www.mytheresa.com/us/en/women/bags and https://www.mytheresa.com/us/en/women/accessories and 3 others all use the title “Women's Luxury Fashion & Designer Shopping | Mytheresa”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://www.mytheresa.com/us/en/women/new-arrivals/current-week, https://www.mytheresa.com/us/en/women/designers, https://www.mytheresa.com/us/en/women/clothing, https://www.mytheresa.com/us/en/women/shoes, https://www.mytheresa.com/us/en/women/bags and https://www.mytheresa.com/us/en/women/accessories and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://www.mytheresa.com/us/en/women/new-arrivals/current-week, https://www.mytheresa.com/us/en/women/designers, https://www.mytheresa.com/us/en/women/clothing, https://www.mytheresa.com/us/en/women/shoes, https://www.mytheresa.com/us/en/women/bags and https://www.mytheresa.com/us/en/women/accessories and 3 others have 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 116 found) and read each the way a search engine does.
3 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 title
All 15 pages that loaded have a <title>.
Best practices
48 small tap targets
48 of 133 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 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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
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: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 989 words of copy
The homepage carries about 989 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
22 cookies set on arrival
22Opening the homepage sets 22 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 mytheresa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Akamai
Company
- Founded
- 2006
- Headquarters
- Munich
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on mytheresa.com, including 22 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.