Website review, no card needed
benjart.com website review
Visit site (opens in a new tab)Reviewed 13 November 202632 issues · 79 checks
This review found 32 issues worth fixing on benjart.com, 7 of them high impact, across 79 checks. The most urgent: no call to action on the first screen. 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
81B- #37,073 of 109,350 reviewed websitesbeats 60%
- #24,698 of 61,859 online storesbeats 54%
- #23,830 of 56,401 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 986 ms |
| Jun 27, 2026 | 911 ms |
| Jul 4, 2026 | 781 ms |
| Jul 11, 2026 | 709 ms |
| Jul 18, 2026 | 702 ms |
| Jul 25, 2026 | 713 ms |
| Aug 1, 2026 | 765 ms |
| Aug 8, 2026 | 758 ms |
| Aug 15, 2026 | 749 ms |
| Aug 22, 2026 | 712 ms |
| Aug 29, 2026 | 704 ms |
| Sep 5, 2026 | 701 ms |
| Sep 12, 2026 | 713 ms |
| Sep 19, 2026 | 739 ms |
| Sep 26, 2026 | 716 ms |
| Oct 3, 2026 | 680 ms |
| Oct 10, 2026 | 671 ms |
| Oct 17, 2026 | 687 ms |
| Oct 24, 2026 | 663 ms |
| Oct 31, 2026 | 671 ms |
| Nov 7, 2026 | 656 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 223 ms |
| May 30, 2026 | 223 ms |
| Jun 6, 2026 | 227 ms |
| Jun 13, 2026 | 226 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 81 ms |
| Aug 8, 2026 | 82 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 79 ms |
| Sep 5, 2026 | 81 ms |
| Sep 12, 2026 | 86 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 88 ms |
| Nov 7, 2026 | 87 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
150 ms · 437 KiB15 images could be 437 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 52 KiB11 files are served with short cache lifetimes, so returning visitors download them again (52 KiB).
Shopify adds 20 ms
20 msShopify costs a phone 20 ms of main-thread work and 382 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.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Snapchat and Shopify and others), adding 838 KiB and 167 ms of main-thread time.
Reduce unused JavaScript
150 ms · 24 KiBAbout 24 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 326 ms of it running JavaScript. That is comfortably low.
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.8 s
7.8 sYour largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Denim Set. Benjart Leather Tab Hoodie and Jogger in was…”.
Time to Interactive: 7.9 s
7.9 sThe page becomes fully interactive after 7.9 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
10 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: 0.6 s
0.6 sReal visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 87 ms
87 msReal visitors wait 87 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 251 ms
251 msReal visitors wait 251 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 61% faster for real visitors
-61%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 223 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, 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
2 images far larger than shown
81 KiB2 images are downloaded at several times the size a phone draws them, for example IMG-5612.webp at 900 px wide, shown at 169 px. Resized copies would save about 81 KiB.
2 images in older formats
2 images (119 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.
About 0.5 g of CO₂ per visit
0.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.54 g of CO₂e: 64.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.9 MB in 170 requests
1.9 MBYour homepage downloads 1.9 MB in 170 requests on a phone: other files 726 KiB (80), images 583 KiB (16) and scripts 470 KiB (60). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
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.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
28 internal links, 2 external
The homepage links to 28 pages on benjart.com and 2 external pages.
4 checks passed
Title: 44 characters
Your title is a healthy 44 characters: “Benjart | Premium Streetwear, Born in the UK”.
Canonical URL set
The canonical URL is https://www.benjart.com/en-us.
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://www.benjart.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 (189 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.benjart.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.benjart.com/en-us and / all use the title “Benjart | Premium Streetwear, Born in the UK”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
/, https://www.benjart.com/collections/new-releases, https://www.benjart.com/collections/blanks, https://www.benjart.com/collections/all, https://www.benjart.com/collections/t-shirts and https://www.benjart.com/collections/short-sets-1 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 links to non-canonical URLs
Your homepage links to 11 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.benjart.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
/ has no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://www.benjart.com/pages/benjartworld, https://www.benjart.com/collections/denim-leather-tab, https://www.benjart.com/en-us/products/benjart-stone-leather-tab-hoodie-denim-blue, https://www.benjart.com/en-us/products/benjart-stone-leather-tab-jogger-denim-blue, https://www.benjart.com/en-us/products/benjart-green-leather-tab-hoodie and https://www.benjart.com/en-us/products/benjart-green-leather-tab-jogger have 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 23 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
14 of 17 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 176 words
The homepage has only about 176 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.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Join”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
25 other companies contacted
Loading the homepage contacts 25 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 benjart.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Omnise Ai Builder · Klaviyo Email Marketing Sms · metizapps.com · campaignified.app · snapchat.com · nfcube.com · useamp.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on benjart.com, including 9 speed issues, 5 SEO issues and 5 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.