Website review, no card needed

clae.com logo

clae.com website review

Visit site (opens in a new tab)Reviewed 9 November 202620 issues · 79 checks

This review found 20 issues worth fixing on clae.com, 6 of them high impact, across 79 checks. The most urgent: 4 tap targets too small. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.4 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20261.8 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
162 ms103 msMay 16Oct 31141 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026110 ms
May 30, 2026111 ms
Jun 6, 2026113 ms
Jun 13, 2026114 ms
Jun 20, 2026118 ms
Jun 27, 2026125 ms
Jul 4, 2026129 ms
Jul 11, 2026132 ms
Jul 18, 2026136 ms
Jul 25, 2026130 ms
Aug 1, 2026130 ms
Aug 8, 2026134 ms
Aug 15, 2026138 ms
Aug 22, 2026146 ms
Aug 29, 2026147 ms
Sep 5, 2026155 ms
Sep 12, 2026152 ms
Sep 19, 2026152 ms
Sep 26, 2026154 ms
Oct 3, 2026146 ms
Oct 10, 2026154 ms
Oct 17, 2026146 ms
Oct 24, 2026146 ms
Oct 31, 2026141 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

1 to fix100
  • Tap response (INP) got 29% slower for real visitors

    +29%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 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: 525 ms

    525 ms

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

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

    -22%

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

Images and page weight

1 to fix85
  • Page weight: 3.5 MB

    3.5 MB

    Your homepage downloads 3.5 MB on a phone, 367 KiB of it images (10%). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

8 to fix90
  • 4 tap targets too small

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

  • 3 text elements with low contrast

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

  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • 2 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

1 to fix93
  • Title is short (13 characters)

    Your title is only 13 characters: “CLAE Footwear”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 228 internal links, 8 external

    The homepage links to 228 pages on clae.com and 8 external pages.

7 checks passed
  • Meta description: 101 characters

    Your meta description is 101 characters: “Shop modern silhouettes that emphasize uncommon comfort and versatility for today's active lifestyle.”.

  • One H1 headline

    Your main headline reads: “CLAE”.

  • Canonical URL set

    The canonical URL is https://clae.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://clae.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no /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.

3 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,424 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    /collections/accessories has no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    /collections/new-collection, /collections/shoes, /blogs/journal/clae-x-union-los-angeles, /products/gift-card, /collections/accessories and /collections/sneakers have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    /products/gift-card has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

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

Best practices

2 to fix87
  • 69 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were 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.

Security and trust

1 to fix93
  • 1 broken external link

    1 link to other sites is dead, for example https://www.youtube.com/@clae_official (404).

  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (clae.com).

  • Valid certificate (47 days left)

    The certificate from Let's Encrypt · YE1 verifies for clae.com and is valid for another 47 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://clae.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

  • No CAA record

    clae.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    clae.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 24 years old

    24 years

    clae.com was registered in May 2002 through Network Solutions, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until May 2028

    clae.com is registered until May 2028.

Content and conversion

3 to fix58
  • 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 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 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 677 words of copy

    The homepage carries about 677 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop Essentials”, “What we make and howBranding Learn More” and “Learn More”.

  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “google”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 30 cookies set on arrival

    30

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

  • 48 other companies contacted

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

Apps on your store

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

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Avada Seo Suite · Wisepops Popup Builder Cro · Klaviyo Email Marketing Sms · Nospy · Geoip Country Redirect · Oxi Social Login Wishlist · Rivo Loyalty Rewards Referrals · Pushowl · Back In Stock · Polar Analytics · global-e.com · nfcube.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
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on clae.com, including 1 speed issue, 1 SEO issue and 3 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