Website review, no card needed
stok.store website review
Visit site (opens in a new tab)Reviewed 16 November 202638 issues · 88 checks
This review found 38 issues worth fixing on stok.store, 13 of them high impact, across 88 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
73C- #90,331 of 122,147 reviewed websitesbeats 22%
- #56,504 of 69,026 online storesbeats 15%
- #52,919 of 62,886 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.3 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 135 ms |
| Jun 6, 2026 | 133 ms |
| Jun 13, 2026 | 130 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 134 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 140 ms |
| Aug 1, 2026 | 141 ms |
| Aug 8, 2026 | 143 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 147 ms |
| Sep 19, 2026 | 149 ms |
| Sep 26, 2026 | 149 ms |
| Oct 3, 2026 | 149 ms |
| Oct 10, 2026 | 151 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 158 ms |
| Oct 31, 2026 | 163 ms |
| Nov 7, 2026 | 168 ms |
| Nov 14, 2026 | 170 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
Reduce unused JavaScript
1.4 s · 697 KiBAbout 697 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
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.
Main-thread work: 8.0 s
A phone's processor spends 8.0 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,935 HTML elements
The page has 5,935 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
4.9 MB177 images could be 4.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, channel.io and Facebook and others), adding 1.6 MB and 1.7 s of main-thread time.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.
Google Tag Manager adds 883 ms
883 msGoogle Tag Manager costs a phone 883 ms of main-thread work and 738 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.
Use efficient cache lifetimes
350 ms · 448 KiB17 files are served with short cache lifetimes, so returning visitors download them again (448 KiB).
Reduce unused CSS
300 ms · 34 KiBAbout 34 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
channel.io adds 297 ms
297 mschannel.io costs a phone 297 ms of main-thread work and 310 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.
Render-blocking requests
300 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Facebook adds 264 ms
264 msFacebook costs a phone 264 ms of main-thread work and 278 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.
Minify JavaScript
280 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Legacy JavaScript
64 KiBPolyfills for old browsers add 64 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: 38 ms
38 msYour server sent the HTML in 38 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: 9.5 s
9.5 sYour largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “https://cdn.snkrdunk.com/uploads/media/1d55085b-3529-4da6-9…”.
Time to Interactive: 21.5 s
21.5 sThe page becomes fully interactive after 21.5 s. Good is under 3.8 s.
Total Blocking Time: 2.5 s
2.5 sScripts block taps and scrolling for 2.5 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.0 s
9.0 sVisually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.
Real-user INP: 280 ms
280 msReal visitors wait 280 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 135 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 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.
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 571 ms
571 msReal visitors wait 571 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.9 MB in 416 requests
9.9 MBYour homepage downloads 9.9 MB in 416 requests on a phone: images 7.4 MB (241), scripts 2.2 MB (55) and HTML 111 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (47 KiB) is 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 2.8 g of CO₂ per visit
2.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.79 g of CO₂e: 335.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
146 text elements with low contrast
146 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (260 elements).
2 checks passed
Every image has alt text
All 903 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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
550 internal links, 15 external
The homepage links to 550 pages on stok.store and 15 external pages.
8 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “【鑑定つき】スニーカー、トレカ、アパレル、アクセサリーが買える・売れる!スニーカーダンクはプロ鑑定士の真贋鑑定&全額補償付きの安心・安全な取引でお届け。人気の新作からレアな古着・中古アイテムまで豊富な品揃え。買取サービスも強化中!”.
One H1 headline
Your main headline reads: “SNKRDUNK”.
Title: 53 characters
Your title is a healthy 53 characters: “スニーカーダンク(スニダン) | 人気新作のスニーカー、トレカ、注目アパレル、アクセの安心売買フリマアプリ”.
Canonical URL set
The canonical URL is https://snkrdunk.com/.
Structured data in place
Structured data found: 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://snkrdunk.com/en/sitemap/sitemap-index-en-main.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://snkrdunk.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 (3,073 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages without an H1
https://snkrdunk.com/categories/2, https://snkrdunk.com/categories/1, https://snkrdunk.com/categories/6, https://snkrdunk.com/brands/supreme, https://snkrdunk.com/brands/chrome-hearts and https://snkrdunk.com/brands/humanmade and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages with very little text
https://snkrdunk.com/categories/2, https://snkrdunk.com/categories/1, https://snkrdunk.com/categories/6, https://snkrdunk.com/information and https://snkrdunk.com/brands 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 188 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 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 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 403 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
166 of 177 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 14 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 2,631 words of copy
The homepage carries about 2,631 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 3 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
22 other companies contacted
Loading the homepage contacts 22 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 stok.store, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- E-commerce
- Shopify;Shopify Plus
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Hiring
- Hiring
- 3 open roles
- Teams
- Commissioning (2), Carbon Services (1)
- Job board
- greenhouse
- Careers page
- boards.greenhouse.io/stok (opens in a new tab)
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 stok.store, including 22 speed issues and 6 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.