Website review, no card needed

aimeleondore.com logo

aimeleondore.com website review

Visit site (opens in a new tab)Reviewed 18 October 202630 issues · 76 checks

This review found 30 issues worth fixing on aimeleondore.com, 7 of them high impact, across 76 checks. The most urgent: no call to action on the first screen. 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.0 s1.2 sApr 25Oct 101.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.7 s
May 2, 20261.7 s
May 9, 20261.8 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
130 ms95 msApr 25Oct 10120 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026121 ms
May 2, 2026122 ms
May 9, 2026126 ms
May 16, 2026124 ms
May 23, 2026126 ms
May 30, 2026121 ms
Jun 6, 2026120 ms
Jun 13, 2026120 ms
Jun 20, 2026121 ms
Jun 27, 2026121 ms
Jul 4, 2026121 ms
Jul 11, 2026113 ms
Jul 18, 2026112 ms
Jul 25, 2026108 ms
Aug 1, 2026103 ms
Aug 8, 2026100 ms
Aug 15, 202699 ms
Aug 22, 2026100 ms
Aug 29, 2026104 ms
Sep 5, 2026112 ms
Sep 12, 2026112 ms
Sep 19, 2026117 ms
Sep 26, 2026120 ms
Oct 3, 2026121 ms
Oct 10, 2026120 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 aimeleondore.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aimeleondore.com at 0.4 s0.4 s
  2. aimeleondore.com at 0.8 s0.8 s
  3. aimeleondore.com at 1.1 s1.1 s
  4. aimeleondore.com at 1.5 s1.5 s
  5. aimeleondore.com at 1.9 s1.9 s
  6. aimeleondore.com at 2.3 s2.3 s
  7. aimeleondore.com at 2.6 s2.6 s
  8. aimeleondore.com at 3.0 s3.0 s

Speed

8 to fix63
  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    710 ms · 268 KiB

    About 268 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 710 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Bugsnag, Google Tag Manager and Shopify and others), adding 973 KiB and 723 ms of main-thread time.

  • Render-blocking requests

    700 ms

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

  • Bugsnag adds 457 ms

    457 ms

    Bugsnag costs a phone 457 ms of main-thread work and 14 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

    410 ms · 21 KiB

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

  • Main-thread work: 2.4 s

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

  • Shopify adds 61 ms

    61 ms

    Shopify costs a phone 61 ms of main-thread work and 425 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.

  • Use efficient cache lifetimes

    150 ms · 77 KiB

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

  • 3 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • 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

4 to fix100
  • Largest Contentful Paint: 11.4 s

    11.4 s

    Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We, along with third parties, use cookies to facilitate you…”.

  • Time to Interactive: 16.8 s

    16.8 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Tap response (INP) held steady for real visitors

    -1%

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

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

    2.0 s

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

  • Real-user INP: 110 ms

    110 ms

    Real visitors wait 110 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.1 s

    1.1 s

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

  • Real-user TTFB: 449 ms

    449 ms

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

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

    -23%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 48 ms

    48 ms

    Scripts block the page for only 48 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 3.1 MB in 338 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 338 requests on a phone: other files 1.5 MB (247), scripts 1.0 MB (70) and images 334 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

4 to fixGoogle 9594
  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 2 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 10089
  • Title is short (14 characters)

    Your title is only 14 characters: “Aimé Leon Dore”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 71 internal links, 2 external

    The homepage links to 71 pages on aimeleondore.com and 2 external pages.

6 checks passed
  • Meta description: 92 characters

    Your meta description is 92 characters: “Created in 2014, Aimé Leon Dore is a fashion and lifestyle brand based out of New York City.”.

  • One H1 headline

    Your main headline reads: “Aimé Leon Dore”.

  • Canonical URL set

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

  • 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.aimeleondore.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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.

  • llms.txt published

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

Other pages

2 to fix93
  • 4 pages share a meta description

    https://www.aimeleondore.com/collections/new-arrivals, https://www.aimeleondore.com/collections/curatedselects, https://www.aimeleondore.com/collections/womens and https://www.aimeleondore.com/collections/swim use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://www.aimeleondore.com/collections/shop-all, https://www.aimeleondore.com/collections/new-arrivals, https://www.aimeleondore.com/collections/curatedselects, https://www.aimeleondore.com/collections/uniform, https://www.aimeleondore.com/collections/womens and https://www.aimeleondore.com/collections/tees and 8 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 40 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 29 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Only about 68 words

    The homepage has only about 68 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “SHOP AIMELEONDORE.COM”, “Shop All” and “Shop”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 aimeleondore.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
jQuery
E-commerce
Shopify

Hiring

Hiring
14 open roles
Teams
Retail (3), Cafe (1), Marketing (1), Production /PD (1)
Job board
greenhouse

Company

Founded
2014

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on aimeleondore.com, including 12 speed issues, 2 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