Website review, no card needed
xyxxcrew.com website review
Visit site (opens in a new tab)Reviewed 4 November 202636 issues · 83 checks
This review found 36 issues worth fixing on xyxxcrew.com, 8 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
82B- #33,154 of 117,615 reviewed websitesbeats 66%
- #22,156 of 66,923 online storesbeats 60%
- #21,424 of 61,018 Shopify storesbeats 58%
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.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 259 ms |
| May 23, 2026 | 259 ms |
| May 30, 2026 | 260 ms |
| Jun 6, 2026 | 269 ms |
| Jun 13, 2026 | 271 ms |
| Jun 20, 2026 | 273 ms |
| Jun 27, 2026 | 276 ms |
| Jul 4, 2026 | 274 ms |
| Jul 11, 2026 | 275 ms |
| Jul 18, 2026 | 274 ms |
| Jul 25, 2026 | 269 ms |
| Aug 1, 2026 | 255 ms |
| Aug 8, 2026 | 247 ms |
| Aug 15, 2026 | 240 ms |
| Aug 22, 2026 | 241 ms |
| Aug 29, 2026 | 246 ms |
| Sep 5, 2026 | 246 ms |
| Sep 12, 2026 | 242 ms |
| Sep 19, 2026 | 236 ms |
| Sep 26, 2026 | 233 ms |
| Oct 3, 2026 | 231 ms |
| Oct 10, 2026 | 233 ms |
| Oct 17, 2026 | 234 ms |
| Oct 24, 2026 | 233 ms |
| Oct 31, 2026 | 232 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
Speed
Render-blocking requests
1.4 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
3,728 HTML elements
The page has 3,728 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
499 KiB49 images could be 499 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
150 ms · 18 KiB7 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).
8 third-party services on the page
8 third-party services load with your homepage (JSDelivr CDN, Shopify and Cloudflare CDN and others), adding 484 KiB and 1 ms of main-thread time.
Reduce unused CSS
15 KiBAbout 15 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 56 ms of it running JavaScript. That is comfortably low.
Server response: 14 ms
14 msYour server sent the HTML in 14 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.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 7.6 s
7.6 sThe page becomes fully interactive after 7.6 s. Good is under 3.8 s.
Real-user INP: 234 ms
234 msReal visitors wait 234 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 73% slower for real visitors
+73%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 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 TTFB: 790 ms
790 msReal visitors wait 790 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 259 ms to 232 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.3 s
2.3 sVisually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.7 MB in 206 requests
2.7 MBYour homepage downloads 2.7 MB in 206 requests on a phone: images 1.8 MB (129), scripts 610 KiB (37) and stylesheets 102 KiB (34). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (887 KiB) 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 far larger than shown
38 KiB1 image is downloaded at several times the size a phone draws it, for example icon_01.svg at 250 px wide, shown at 40 px. Resized copies would save about 38 KiB.
3 images below the first screen load straight away
3 images further down the page (168 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
90 tap targets too small
90 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
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.
1 form field without a label
1 form field has 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 101 images in the HTML carry an alt attribute.
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “India's Most Loved Men’s Innerwear, Athleisure & Clothing Brand – XYXX Apparels”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
366 internal links, 9 external
The homepage links to 366 pages on xyxxcrew.com and 9 external pages.
6 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Upgrade your essentials with premium men’s underwear, loungewear and athleisure. Discover breathable fabrics and everyd…”.
Canonical URL set
The canonical URL is https://xyxxcrew.com/.
Structured data in place
Structured data found: FAQPage, 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://xyxxcrew.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://xyxxcrew.com/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,607 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://xyxxcrew.com/collections/all and https://xyxxcrew.com/collections/winter-must-have have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://xyxxcrew.com/collections/all, https://xyxxcrew.com/collections/winter-must-have, https://xyxxcrew.com/collections/t-shirts-for-men, https://xyxxcrew.com/collections/hoodies-for-men, https://xyxxcrew.com/collections/jackets-for-men-1 and https://xyxxcrew.com/collections/underwear-for-men and 1 other 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 122 found) and read each the way a search engine does.
5 checks passed
Linked pages load
8 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 8 pages that loaded have a <title>.
Best practices
62 small tap targets
62 of 125 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot use import statement outside a module”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. 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.
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 1,928 words of copy
The homepage carries about 1,928 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Download Now” and “Shop here Flannel Shirt - Autumn Red”.
5 calls to action
The homepage has 5 calls to action, for example “Download Now”, “Shop By Category” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
24 cookies set on arrival
24Opening the homepage sets 24 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.
41 other companies contacted
Loading the homepage contacts 41 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 xyxxcrew.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
- Vue.js
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Surat
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on xyxxcrew.com, including 12 speed issues, 4 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.