Website review, no card needed
myonecondoms.hk website review
Visit site (opens in a new tab)Reviewed 21 November 202643 issues · 80 checks
This review found 43 issues worth fixing on myonecondoms.hk, 20 of them high impact, across 80 checks. The most urgent: render-blocking 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
61D- #119,749 of 123,845 reviewed websitesbeats 3%
- #68,831 of 69,695 online storesbeats 1%
- #62,806 of 63,403 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
3.9 s
7.8 s
11.8 s
15.7 s
19.6 s
23.5 s
27.5 s
31.4 s
Speed
Render-blocking requests
2.8 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Use efficient cache lifetimes
1.6 s · 197 KiB14 files are served with short cache lifetimes, so returning visitors download them again (197 KiB).
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
580 ms · 117 KiBAbout 117 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 580 ms faster on a phone.
Improve image delivery
450 ms · 188 KiB7 images could be 188 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.
Legacy JavaScript
450 ms · 42 KiBPolyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (weglot.com, Klaviyo and cloudfront.net and others), adding 698 KiB and 472 ms of main-thread time.
Reduce unused CSS
130 ms · 11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 130 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 95 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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 944 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: 12.2 s
12.2 sYour largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.53
0.53The layout shifts by 0.53 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 12.2 s
12.2 sThe page becomes fully interactive after 12.2 s. Good is under 3.8 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 76 ms
76 msScripts block the page for only 76 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 194 requests
2.2 MBYour homepage downloads 2.2 MB in 194 requests on a phone: other files 972 KiB (89), scripts 675 KiB (59) and images 463 KiB (26). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
3 KiB1 image is downloaded at several times the size a phone draws it, for example Animal_banner-CN_2048x2048.progressive.png.jpg at 1,199 px wide, shown at 390 px. Resized copies would save about 3 KiB.
3 images below the first screen load straight away
3 images further down the page (148 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
ARIA toggle fields must have an accessible name (1 element)
ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 14 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, NOFOLLOW”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“”, “Introducing myONE® Perfect Fit condoms.” and “Does size matter?”). One clear main headline is easier for people and search engines.
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:description, so shared links fall back to guesses.
34 internal links, 8 external
The homepage links to 34 pages on myonecondoms.hk and 8 external pages.
4 checks passed
Title: 37 characters
Your title is a healthy 37 characters: “Condom Sizes for Everyone – myONE® HK”.
Canonical URL set
The canonical URL is https://www.myonecondoms.hk/.
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.myonecondoms.hk/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 (698 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.myonecondoms.hk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 linked pages hidden from search
https://www.myonecondoms.hk/pages/our-products, https://www.myonecondoms.hk/pages/get-started, https://www.myonecondoms.hk/pages/customer-reviews, https://www.myonecondoms.hk/pages/help-center, https://www.myonecondoms.hk/pages/find-your-fit and https://www.myonecondoms.hk/pages/myone-condom-samplers and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
7 pages without a meta description
https://www.myonecondoms.hk/pages/our-products, https://www.myonecondoms.hk/pages/get-started, https://www.myonecondoms.hk/pages/customer-reviews, https://www.myonecondoms.hk/pages/find-your-fit, https://www.myonecondoms.hk/pages/myone-condom-samplers and https://www.myonecondoms.hk/pages/contact-us and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 13 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 736 words of copy
The homepage carries about 736 words of visible text.
3 checks passed
9 calls to action
The homepage has 9 calls to action, for example “Get Started”, “Try Our Sample Kit” and “Contact us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and Xandr (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (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.
32 other companies contacted
Loading the homepage contacts 32 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 myonecondoms.hk, 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
rechargecdn.com · weglot.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
- Framework
- jQuery
- 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 43 issues on myonecondoms.hk, including 12 speed issues, 6 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.