Website review, no card needed
catoriclothing.com website review
Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 85 checks
This review found 38 issues worth fixing on catoriclothing.com, 13 of them high impact, across 85 checks. The most urgent: mobile performance score: 48. 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
83B- #28,588 of 125,955 reviewed websitesbeats 72%
- #18,546 of 70,316 online storesbeats 67%
- #17,950 of 63,859 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.2 s |
| Jul 4, 2026 | 1.1 s |
| Jul 18, 2026 | 945 ms |
| Jul 25, 2026 | 834 ms |
| Aug 1, 2026 | 855 ms |
| Aug 8, 2026 | 858 ms |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 24, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 130 ms |
| Jul 4, 2026 | 146 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 146 ms |
| Sep 12, 2026 | 198 ms |
| Sep 19, 2026 | 181 ms |
| Oct 24, 2026 | 146 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.1 s
4.1 s
5.1 s
6.1 s
7.2 s
8.2 s
Speed
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.5 s
A phone's processor spends 8.5 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,247 HTML elements
The page has 4,247 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Hotjar, Google Tag Manager and Cloudflare CDN and others), adding 1.3 MB and 1.6 s of main-thread time.
Improve image delivery
400 ms · 685 KiB20 images could be 685 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Render-blocking requests
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 661 ms. During a long task the page ignores taps.
Hotjar adds 602 ms
602 msHotjar costs a phone 602 ms of main-thread work and 65 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.
Google Tag Manager adds 399 ms
399 msGoogle Tag Manager costs a phone 399 ms of main-thread work and 296 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 JavaScript
428 KiBAbout 428 KiB of JavaScript is downloaded but never used on this page.
Cloudflare CDN adds 204 ms
204 msCloudflare CDN costs a phone 204 ms of main-thread work and 427 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
150 ms · 51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
169 KiB13 files are served with short cache lifetimes, so returning visitors download them again (169 KiB).
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify JavaScript
21 KiB21 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 146 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 this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.019
0.019The layout barely moves while loading (CLS 0.019, good is under 0.1).
Images and page weight
2 images over 500 KB
2 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.
Page weight: 5.4 MB in 243 requests
5.4 MBYour homepage downloads 5.4 MB in 243 requests on a phone: images 2.6 MB (37), scripts 1.5 MB (93) and other files 1,005 KiB (103). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
525 KiB2 images are downloaded at several times the size a phone draws them, for example 283fc7df-16a1-4401-97c0-3c9b009d6dd4.jpeg at 2,059 px wide, shown at 320 px. Resized copies would save about 525 KiB.
2 images in older formats
2 images (5.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
1 image below the first screen load straight away
1 image further down the page (95 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (82 characters)
Your title is 82 characters, so Google will cut it off around 60: “Catori - Graphic Apparel, Clothing & Streetwear | Anime Clothing – Catori Clothing”.
Meta description is long (282 characters)
Your meta description is 282 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
127 internal links, 11 external
The homepage links to 127 pages on catoriclothing.com and 11 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Catori Clothing”.
Canonical URL set
The canonical URL is https://catoriclothing.com/.
Structured data in place
Structured data found: FAQPage.
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://catoriclothing.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (3,807 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://catoriclothing.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://catoriclothing.com/collections/the-finale, https://catoriclothing.com/collections/dec-23 and https://catoriclothing.com/collections/august-23 have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://catoriclothing.com/collections/shop and https://catoriclothing.com/pages/contact-us 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 87 found) and read each the way a search engine does.
5 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.
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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187023084&tm=shpfy_ui&Ver=2&mid=b25194ae-1b01-4117-8496-11879704a84d&bo=1&sid=21d9a2f0d8d011f1bb95b7be52510320&vid=21d9d4c0d8d011f1b423db2bd11c418e&vids=1&msclkid=N&pi.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “No color options found.”.
2 checks passed
Tap targets are thumb-sized
20 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 2,785 words of copy
The homepage carries about 2,785 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
15 calls to action
The homepage has 15 calls to action, for example “Shop icon-chevron Expand submenu”, “Shop” and “Shop All”.
7 short forms
7 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 mores (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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
38 other companies contacted
Loading the homepage contacts 38 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 catoriclothing.com, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Thoughtmetric · trafficmanager.net · postscript.io · kiwisizing.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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on catoriclothing.com, including 16 speed issues, 3 SEO issues and 1 conversion gap. 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.