Website review, no card needed
kink3d.com website review
Visit site (opens in a new tab)Reviewed 7 November 202624 issues · 71 checks
This review found 24 issues worth fixing on kink3d.com, 6 of them high impact, across 71 checks. The most urgent: 10 text elements with low contrast. 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
86B- #9,837 of 98,268 reviewed websitesbeats 86%
- #5,838 of 53,623 online storesbeats 84%
- #5,658 of 48,647 Shopify storesbeats 83%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 855 ms |
| May 23, 2026 | 818 ms |
| May 30, 2026 | 788 ms |
| Jun 6, 2026 | 769 ms |
| Jun 13, 2026 | 761 ms |
| Jun 20, 2026 | 760 ms |
| Jun 27, 2026 | 771 ms |
| Jul 4, 2026 | 785 ms |
| Jul 11, 2026 | 790 ms |
| Jul 18, 2026 | 794 ms |
| Jul 25, 2026 | 792 ms |
| Aug 1, 2026 | 793 ms |
| Aug 8, 2026 | 798 ms |
| Aug 15, 2026 | 806 ms |
| Aug 22, 2026 | 804 ms |
| Aug 29, 2026 | 804 ms |
| Sep 5, 2026 | 805 ms |
| Sep 12, 2026 | 812 ms |
| Sep 19, 2026 | 805 ms |
| Sep 26, 2026 | 783 ms |
| Oct 3, 2026 | 762 ms |
| Oct 10, 2026 | 735 ms |
| Oct 17, 2026 | 729 ms |
| Oct 24, 2026 | 734 ms |
| Oct 31, 2026 | 732 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 84 ms |
| May 23, 2026 | 84 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 87 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 86 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 83 ms |
| Jul 18, 2026 | 81 ms |
| Jul 25, 2026 | 80 ms |
| Aug 1, 2026 | 81 ms |
| Aug 8, 2026 | 80 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 80 ms |
| Aug 29, 2026 | 80 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 80 ms |
| Sep 19, 2026 | 80 ms |
| Sep 26, 2026 | 81 ms |
| Oct 3, 2026 | 80 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 79 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 79 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
Improve image delivery
450 ms · 964 KiB2 images could be 964 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 75
75/100Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.
2,304 HTML elements
The page has 2,304 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, on.aws and consentmo.com), adding 1.1 MB and 72 ms of main-thread time.
consentmo.com adds 0 ms
0 msconsentmo.com costs a phone 0 ms of main-thread work and 905 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 long task on the main thread
1 long task block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Use efficient cache lifetimes
4 KiB2 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 443 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 6.7 s
6.7 sThe page becomes fully interactive after 6.7 s. Good is under 3.8 s.
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 84 ms to 79 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 80 ms
80 msReal visitors wait 80 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.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 369 ms
369 msReal visitors wait 369 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 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: 28 ms
28 msScripts block the page for only 28 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 247 requests
2.6 MBYour homepage downloads 2.6 MB in 247 requests on a phone: images 1.1 MB (9), other files 993 KiB (153) and scripts 264 KiB (51). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
2 checks passed
Every image has alt text
All 11 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (6 characters)
Your title is only 6 characters: “KINK3D”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
92 internal links, 8 external
The homepage links to 92 pages on kink3d.com and 8 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “KINK3D Cobra® and KINK3D Viper® chastity cages + other premium toys. Designed & manufactured in the USA with cutting-ed…”.
Canonical URL set
The canonical URL is https://kink3d.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://kink3d.com/sitemap.xml.
AI search readiness
4 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 (934 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://kink3d.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://kink3d.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://kink3d.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages without a meta description
https://kink3d.com/collections/all, https://kink3d.com/customer_authentication/redirect, https://kink3d.com/policies/shipping-policy and https://kink3d.com/collections/kink3d-base-rings have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://kink3d.com/collections/chastity-kits and https://kink3d.com/collections/cages use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://kink3d.com/customer_authentication/redirect and https://kink3d.com/collections/chastity-kits 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 43 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.
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.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
13 of 13 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.
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 274 words of copy
The homepage carries about 274 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 kink3d.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Gdpr Backpack
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
Company
- Headquarters
- Berkeley
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on kink3d.com, including 9 speed issues, 3 SEO issues and 4 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.