Programmable

Website review, no card needed

onecondoms.my logo

onecondoms.my website review

Visit site (opens in a new tab)Reviewed 13 November 202629 issues · 74 checks

This review found 29 issues worth fixing on onecondoms.my, 9 of them high impact, across 74 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

77C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.1 s708 msMay 30Oct 10901 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026763 ms
Jun 6, 2026757 ms
Jun 13, 2026757 ms
Jun 20, 2026773 ms
Jun 27, 2026813 ms
Jul 4, 2026832 ms
Jul 11, 2026811 ms
Jul 18, 2026783 ms
Jul 25, 2026790 ms
Aug 1, 2026772 ms
Aug 8, 2026850 ms
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 2026885 ms
Oct 10, 2026901 ms
Real-visitor tap response (INP)75th percentile, phones
78 ms62 msJun 6Aug 164 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 202672 ms
Jun 13, 202675 ms
Jun 20, 202674 ms
Jun 27, 202671 ms
Jul 4, 202676 ms
Jul 11, 202674 ms
Jul 18, 202671 ms
Jul 25, 202673 ms
Aug 1, 202664 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

www.onecondoms.my (opens in a new tab)
Full-page screenshot of onecondoms.my (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. onecondoms.my at 0.4 s0.4 s
  2. onecondoms.my at 0.8 s0.8 s
  3. onecondoms.my at 1.2 s1.2 s
  4. onecondoms.my at 1.6 s1.6 s
  5. onecondoms.my at 2.0 s2.0 s
  6. onecondoms.my at 2.3 s2.3 s
  7. onecondoms.my at 2.7 s2.7 s
  8. onecondoms.my at 3.1 s3.1 s

Speed

5 to fix69

  • Render-blocking requests

    1.8 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.

  • Reduce unused JavaScript

    1.2 s · 305 KiB

    About 305 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Use efficient cache lifetimes

    800 ms · 220 KiB

    18 files are served with short cache lifetimes, so returning visitors download them again (220 KiB).

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    400 ms · 91 KiB

    5 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and Amazon Web Services and others), adding 539 KiB and 270 ms of main-thread time.

  • Reduce unused CSS

    290 ms · 22 KiB

    About 22 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.

  • Minify JavaScript

    170 ms · 7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    50 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

    Web 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: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 361 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix67

  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 9.7 s

    9.7 s

    The page becomes fully interactive after 9.7 s. Good is under 3.8 s.

  • Speed Index: 6.2 s

    6.2 s

    Visually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.

  • 7 images without width and height

    7 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-11-07, real Chrome visitors' tap response (inp) went from 72 ms to 64 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 18% slower for real visitors

    +18%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 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.

3 checks passed

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 28 ms

    28 ms

    Scripts block the page for only 28 ms while loading. Good is under 200 ms.

Images and page weight

100

  • About 0.5 g of CO₂ per visit

    0.50 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 60.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed

  • Page weight: 1.8 MB in 122 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 122 requests on a phone: scripts 750 KiB (38), other files 612 KiB (59) and images 316 KiB (11). That is a lean page.

  • 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

7 to fixGoogle 8389

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

1 checks passed

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9279

  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “ONE® Condoms Online Store | Free Shipping on Orders Over RM30 – ONE® Malaysia”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (196 characters)

    Your meta description is 196 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 56 internal links, 5 external

    The homepage links to 56 pages on onecondoms.my and 5 external pages.

4 checks passed

  • Canonical URL set

    The canonical URL is https://www.onecondoms.my/.

  • 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.onecondoms.my/sitemap.xml.

AI search readiness

1 to fix83

  • 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.

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.

  • llms.txt published

    The site publishes https://www.onecondoms.my/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65

  • 1 linked page is broken

    Your homepage links to https://www.onecondoms.my/pages/myone, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 7 pages without a meta description

    https://www.onecondoms.my/collections/all, https://www.onecondoms.my/collections/condoms, https://www.onecondoms.my/collections/lubricant, https://www.onecondoms.my/pages/community, https://www.onecondoms.my/pages/get-social and https://www.onecondoms.my/pages/army-of-one and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.onecondoms.my/pages/about-us, https://www.onecondoms.my/pages/mission, https://www.onecondoms.my/pages/press, https://www.onecondoms.my/pages/contact-us, https://www.onecondoms.my/pages/partnerships and https://www.onecondoms.my/collections/all and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.onecondoms.my/pages/get-social has 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 25 found) and read each the way a search engine does.

4 checks passed

  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687

  • 2 small tap targets

    2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 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

2 to fix86

  • 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.

  • Only about 137 words

    The homepage has only about 137 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP CONDOMS” and “Contact Us”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Shop” and “Subscribe”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 onecondoms.my, 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

Magical Vacations · chimpstatic.com · amazonaws.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
Analytics
Google Tag Manager
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on onecondoms.my, including 9 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25