Website review, no card needed

cmyclothes.store logo

cmyclothes.store website review

Visit site (opens in a new tab)Reviewed 10 November 202627 issues · 70 checks

This review found 27 issues worth fixing on cmyclothes.store, 5 of them high impact, across 70 checks. The most urgent: page weight: 60.7 MB in 176 requests. 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.6 s1.5 sMay 23Sep 192.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
172 ms113 msMay 23Sep 12151 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026154 ms
May 30, 2026158 ms
Jun 6, 2026165 ms
Jun 13, 2026149 ms
Jun 20, 2026150 ms
Jun 27, 2026155 ms
Jul 4, 2026151 ms
Jul 11, 2026145 ms
Jul 18, 2026140 ms
Jul 25, 2026130 ms
Aug 1, 2026123 ms
Aug 8, 2026128 ms
Aug 15, 2026128 ms
Aug 22, 2026120 ms
Aug 29, 2026130 ms
Sep 5, 2026153 ms
Sep 12, 2026151 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 cmyclothes.store (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix84
  • Mobile performance score: 84

    84/100

    Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    450 ms

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

  • 2,642 HTML elements

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

  • Main-thread work: 2.1 s

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

  • Reduce unused JavaScript

    190 ms · 65 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, Klaviyo and JSDelivr CDN and others), adding 324 KiB and 114 ms of main-thread time.

  • Improve image delivery

    118 KiB

    5 images could be 118 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    19 KiB

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

  • Use efficient cache lifetimes

    11 KiB

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

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

    7 ms

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

Core Web Vitals

3 to fix80
  • Largest Contentful Paint: 4.4 s

    4.4 s

    Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

    +34%

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

  • Time to Interactive: 4.7 s

    4.7 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.003

    0.003

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

  • Total Blocking Time: 27 ms

    27 ms

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

Images and page weight

1 to fix70
  • Page weight: 60.7 MB in 176 requests

    60.7 MB

    Your homepage downloads 60.7 MB in 176 requests on a phone: media 59.2 MB (11), other files 712 KiB (71) and scripts 415 KiB (58). Under 2 MB keeps phones on slow connections fast.

  • About 17.2 g of CO₂ per visit

    17.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 17.22 g of CO₂e: 2065.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 8994
  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • 10 text elements with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

5 to fixGoogle 10078
  • Title is short (12 characters)

    Your title is only 12 characters: “CMY HOMEPAGE”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (55 characters)

    Your meta description is only 55 characters: “STÜSSY jersey STÜSSY jersey football kits STÜSSY Brazil”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • 30 internal links, 1 external

    The homepage links to 30 pages on cmyclothes.store and 1 external page.

4 checks passed
  • Canonical URL set

    The canonical URL is https://cmyclothes.store/.

  • Structured data in place

    Structured data found: Organization 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://cmyclothes.store/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

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

Other pages

3 to fix85
  • 13 pages without a meta description

    https://cmyclothes.store/collections/frontpage, https://cmyclothes.store/collections/2026worldcup, https://cmyclothes.store/collections/windbreakers, https://cmyclothes.store/collections/childer-sizes, https://cmyclothes.store/collections/retro-kits and https://cmyclothes.store/collections/cmy-collection/ST%C3%9CSSY-collection and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://cmyclothes.store/collections/cmy-collection/ST%C3%9CSSY-collection, whose canonical is https://cmyclothes.store/collections/cmy-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://cmyclothes.store/collections/frontpage, https://cmyclothes.store/collections/2026worldcup, https://cmyclothes.store/collections/windbreakers, https://cmyclothes.store/collections/childer-sizes, https://cmyclothes.store/collections/retro-kits and https://cmyclothes.store/collections/cmy-collection/ST%C3%9CSSY-collection and 7 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 21 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

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

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

    7 of 33 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

4 to fix71
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. 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 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 118 words

    The homepage has only about 118 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.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “CONTACT”, “TRACK YOUR ORDER” and “SHOP NOW”.

  • 9 short forms

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Klaviyo, Meta Pixel, Pinterest Tag and TikTok 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.

  • 14 cookies set on arrival

    14

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 cmyclothes.store, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

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

Apps your storefront loads

Gsc Countdown Timer · Seowill Ai Seo · Klaviyo Email Marketing Sms · Trueprofit · Glo Color Swatch · Deco Labels Badges · cloudfront.net · wetracked.io

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

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on cmyclothes.store, including 7 speed issues, 5 SEO issues and 4 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