Website review, no card needed
chetrock.com website review
Visit site (opens in a new tab)Reviewed 17 November 202625 issues · 76 checks
This review found 25 issues worth fixing on chetrock.com, 6 of them high impact, across 76 checks. The most urgent: page weight: 5.7 MB in 281 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
88B- #5,556 of 116,020 reviewed websitesbeats 93%
- #3,100 of 66,707 online storesbeats 93%
- #3,006 of 60,900 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 950 ms |
| Jun 6, 2026 | 940 ms |
| Jun 13, 2026 | 929 ms |
| Jun 20, 2026 | 905 ms |
| Jun 27, 2026 | 910 ms |
| Jul 4, 2026 | 933 ms |
| Jul 11, 2026 | 925 ms |
| Jul 18, 2026 | 961 ms |
| Jul 25, 2026 | 965 ms |
| Aug 1, 2026 | 959 ms |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 963 ms |
| Aug 22, 2026 | 967 ms |
| Aug 29, 2026 | 976 ms |
| Sep 5, 2026 | 951 ms |
| Sep 12, 2026 | 969 ms |
| Sep 19, 2026 | 957 ms |
| Sep 26, 2026 | 953 ms |
| Oct 3, 2026 | 964 ms |
| Oct 10, 2026 | 949 ms |
| Oct 17, 2026 | 968 ms |
| Oct 24, 2026 | 969 ms |
| Oct 31, 2026 | 966 ms |
| Nov 7, 2026 | 975 ms |
| Nov 14, 2026 | 957 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 156 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 158 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 160 ms |
| Aug 15, 2026 | 156 ms |
| Aug 22, 2026 | 162 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 163 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 166 ms |
| Oct 3, 2026 | 157 ms |
| Oct 10, 2026 | 143 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 136 ms |
| Nov 7, 2026 | 135 ms |
| Nov 14, 2026 | 133 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
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
2.9 MB49 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Clarity and salesfire.co.uk and others), adding 513 KiB and 783 ms of main-thread time.
Klaviyo adds 244 ms
244 msKlaviyo costs a phone 244 ms of main-thread work and 315 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.
1,870 HTML elements
The page has 1,870 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 152 ms. During a long task the page ignores taps.
Reduce unused JavaScript
95 KiBAbout 95 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
80 KiB12 files are served with short cache lifetimes, so returning visitors download them again (80 KiB).
Duplicated JavaScript
30 KiB30 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need.
Reduce unused CSS
16 KiBAbout 16 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.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.7 s
10.7 sThe page becomes fully interactive after 10.7 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SHOP NEW IN”. Most of its time is element render delay (2.4 s).
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 146 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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 INP: 128 ms
128 msReal visitors wait 128 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.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 480 ms
480 msReal visitors wait 480 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 163 ms
163 msScripts block the page for only 163 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 281 requests
5.7 MBYour homepage downloads 5.7 MB in 281 requests on a phone: images 4.2 MB (82), other files 701 KiB (96) and scripts 646 KiB (81). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
294 KiB3 images are downloaded at several times the size a phone draws them, for example ap-press-kerrang.png at 2,170 px wide, shown at 128 px. Resized copies would save about 294 KiB.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 192.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 167 images in the HTML carry an alt attribute.
48 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: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
200 internal links, 3 external
The homepage links to 200 pages on chetrock.com and 3 external pages.
5 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Alternative style meets British streetwear. Shop Chet Rock clothing today with worldwide shipping and free Delivery on …”.
Title: 30 characters
Your title is a healthy 30 characters: “Chet Rock | British Streetwear”.
Canonical URL set
The canonical URL is https://chetrock.com/.
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://chetrock.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.
No llms.txt
There is no https://chetrock.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.
2 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 (793 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://chetrock.com/collections/all-new-in 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 55 found) and read each the way a search engine does.
6 checks passed
Linked pages load
2 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.
Every page has a meta description
All 2 pages 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 2 pages that loaded have a <title>.
Best practices
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 ()”.
2 checks passed
Tap targets are thumb-sized
172 of 183 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 551 words of copy
The homepage carries about 551 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NEW IN”.
6 calls to action
The homepage has 6 calls to action, for example “Shop All”, “View all Shop All” and “SHOP NEW IN”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
29 other companies contacted
Loading the homepage contacts 29 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 chetrock.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · nfcube.com · salesfire.co.uk
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
- 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 25 issues on chetrock.com, including 10 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.