Website review, no card needed
bench.clothing website review
Visit site (opens in a new tab)Reviewed 16 November 202643 issues · 84 checks
This review found 43 issues worth fixing on bench.clothing, 19 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
65D- #109,174 of 117,615 reviewed websitesbeats 6%
- #64,565 of 66,923 online storesbeats 3%
- #59,250 of 61,018 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
4.4 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.4 s faster on a phone.
Use efficient cache lifetimes
3.2 s · 1.4 MB22 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Signyfyd adds 1.2 s
1.2 sSignyfyd costs a phone 1.2 s of main-thread work and 282 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 10.1 s
A phone's processor spends 10.1 s on main-thread work while loading, 5.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,299 HTML elements
The page has 3,299 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 (Signyfyd, Shopify and route.com and others), adding 3.7 MB and 3.5 s of main-thread time.
Shopify adds 953 ms
953 msShopify costs a phone 953 ms of main-thread work and 1.2 MB 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.
Render-blocking requests
750 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
route.com adds 545 ms
545 msroute.com costs a phone 545 ms of main-thread work and 1.1 MB 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 620 ms. During a long task the page ignores taps.
Improve image delivery
350 ms · 193 KiB8 images could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Duplicated JavaScript
495 KiB495 KiB JavaScript is shipped twice across bundles.
Klaviyo adds 154 ms
154 msKlaviyo costs a phone 154 ms of main-thread work and 318 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
290 ms · 130 KiBAbout 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
Legacy JavaScript
150 ms · 82 KiBPolyfills for old browsers add 82 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
Minify JavaScript
6 KiB6 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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 24.0 s
24.0 sYour largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 19.5 s
19.5 sVisually, the page fills in at 19.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 39.2 s
39.2 sThe page becomes fully interactive after 39.2 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0.068
0.068The layout barely moves while loading (CLS 0.068, good is under 0.1).
Images and page weight
Page weight: 7.4 MB in 525 requests
7.4 MBYour homepage downloads 7.4 MB in 525 requests on a phone: scripts 3.6 MB (256), images 2.2 MB (85) and other files 948 KiB (149). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
62 KiB1 image is downloaded at several times the size a phone draws it, for example EcommBench-BMGP44533-01_1024x1024.jpg at 771 px wide, shown at 30 px. Resized copies would save about 62 KiB.
1 image below the first screen load straight away
1 image further down the page (63 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.09 g of CO₂e: 250.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Hidden but focusable
20 elements hidden from screen readers can still receive keyboard focus.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 tap targets too small
7 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
94 images without alt text
94 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (48 elements)
All page content should be contained by landmarks: 48 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
49 links without text
49 visible links have no text or label, so screen readers cannot say where they go.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to bench.ca, not bench.clothing, so Google may credit that host instead.
2 H1 headlines
There are 2 <h1> headlines (“Bench” and “Search”). One clear main headline is easier for people and search engines.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
188 internal links, 5 external
The homepage links to 188 pages on bench.clothing and 5 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Shop sporty, stylish & comfy t-shirts, sweatpants, hoodies, tracksuits, shorts, leggings and more. Suitable for active …”.
Title: 53 characters
Your title is a healthy 53 characters: “Bench Clothing | Men & Women's Trendy Athleisure Wear”.
Structured data in place
Structured data found: 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://benchcanada.myshopify.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 (669 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bench.clothing/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://bench.clothing/collections/women has 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 91 found) and read each the way a search engine does.
6 checks passed
Linked pages load
1 page 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 1 page 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 1 page that loaded have a <title>.
Best practices
22 small tap targets
22 of 67 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: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 495 words of copy
The homepage carries about 495 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop Sale”, “Shop Women” and “Shop Men”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 47 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Amplitude, 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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
53 other companies contacted
Loading the homepage contacts 53 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 bench.clothing, 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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Boost Ai Search Filter · Seowill Redirects · Klaviyo Email Marketing Sms · Okendo · Consentik Cookie · Multifeeds · Gorgias Live Chat Helpdesk · Route Protection Tracking · Langify · Wishlist By Square · Consentik Ex · Product Labels And Badges · Automatic Discounts Upsells · rise-ai.com · signifyd.com · avada.io · herokuapp.com · tabarn.app · 9gtb.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on bench.clothing, including 20 speed issues, 3 SEO issues and 2 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.