Website review, no card needed
k-y.com website review
Visit site (opens in a new tab)Reviewed 8 November 202636 issues · 79 checks
This review found 36 issues worth fixing on k-y.com, 16 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
70C- #96,490 of 115,229 reviewed websitesbeats 14%
- #59,769 of 66,438 online storesbeats 8%
- #55,544 of 60,755 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 128 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 125 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 139 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 136 ms |
| Oct 17, 2026 | 136 ms |
| Oct 24, 2026 | 137 ms |
| Oct 31, 2026 | 137 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
28.1 s · 6.5 MB8 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 28.1 s faster on a phone.
Use efficient cache lifetimes
3.5 s · 707 KiB10 files are served with short cache lifetimes, so returning visitors download them again (707 KiB).
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Optanon, Google Tag Manager and mikmak.ai and others), adding 5.6 MB and 444 ms of main-thread time.
Render-blocking requests
700 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Reduce unused JavaScript
150 ms · 445 KiBAbout 445 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.
Optanon adds 243 ms
243 msOptanon costs a phone 243 ms of main-thread work and 1.7 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.
contentstack.com adds 0 ms
0 mscontentstack.com costs a phone 0 ms of main-thread work and 3.5 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Reduce unused CSS
64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 26 ms
26 msYour server sent the HTML in 26 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.
Real-user CLS: 0.41
0.41For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 41.7 s
41.7 sYour largest element takes 41.7 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 47.1 s
47.1 sThe page becomes fully interactive after 47.1 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.336
0.336The layout shifts by 0.336 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 940 ms
940 msReal visitors wait 940 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 378 ms
378 msScripts block taps and scrolling for 378 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 128 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 10.1 MB in 65 requests
10.1 MBYour homepage downloads 10.1 MB in 65 requests on a phone: images 7.1 MB (15), scripts 2.4 MB (17) and other files 290 KiB (23). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 3.4 MB together. On a phone connection a single image that size takes seconds.
1 image far larger than shown
815 KiB1 image is downloaded at several times the size a phone draws it, for example reckitt-logo.png at 3,840 px wide, shown at 120 px. Resized copies would save about 815 KiB.
3 images in older formats
3 images (3.4 MB) 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.
1 image below the first screen load straight away
1 image further down the page (822 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.9 g of CO₂ per visit
2.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.86 g of CO₂e: 343.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 19 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
32 internal links, 11 external
The homepage links to 32 pages on k-y.com and 11 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Discover K-Y®'s lubes, gels, and sprays. Reignite that spark in the bedroom with our sexual products and explore sexual…”.
One H1 headline
Your main headline reads: “Personal Lubes, Endurance & Pleasure Products”.
Title: 52 characters
Your title is a healthy 52 characters: “Personal Lubes, Endurance & Pleasure Products | K-Y®”.
Canonical URL set
The canonical URL is https://www.k-y.com/.
Structured data in place
Structured data found: Organization and WebPage.
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://www.k-y.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, 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://www.k-y.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 (635 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a title
https://www.k-y.com/collections/lubes, https://www.k-y.com/collections/enhancements-duration-spray-gel, https://www.k-y.com/products/k-y-yours-mine-couples-lube, https://www.k-y.com/products/k-y-natural-feeling-personal-lube-with-aloe-vera, https://www.k-y.com/products/k-y-intense-pleasure-gel-lube and https://www.k-y.com/sex-health-blog and 9 others have no <title>, so Google invents the link text in results.
15 pages without an H1
https://www.k-y.com/collections/lubes, https://www.k-y.com/collections/enhancements-duration-spray-gel, https://www.k-y.com/products/k-y-yours-mine-couples-lube, https://www.k-y.com/products/k-y-natural-feeling-personal-lube-with-aloe-vera, https://www.k-y.com/products/k-y-intense-pleasure-gel-lube and https://www.k-y.com/sex-health-blog and 9 others 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 17 found) and read each the way a search engine does.
4 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
17 small tap targets
17 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 543 words of copy
The homepage carries about 543 words of visible text.
3 checks passed
9 calls to action
The homepage has 9 calls to action, for example “SHOP”, “More SHOP” and “BUY NOW”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 k-y.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Gatsby
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Analytics
- Google Tag Manager
- Hosting
- Firebase Hosting
Company
- Founded
- 1904
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on k-y.com, including 20 speed 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.