Website review, no card needed

durex.com.ph logo

durex.com.ph website review

Visit site (opens in a new tab)Reviewed 7 November 202618 issues · 67 checks

This review found 18 issues worth fixing on durex.com.ph, 5 of them high impact, across 67 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Real-visitor load time (LCP)75th percentile, phones
2.3 s2.1 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.2 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
126 ms109 msMay 16Oct 31117 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026111 ms
May 30, 2026117 ms
Jun 6, 2026116 ms
Jun 13, 2026116 ms
Jun 20, 2026117 ms
Jun 27, 2026115 ms
Jul 4, 2026119 ms
Jul 11, 2026117 ms
Jul 18, 2026115 ms
Jul 25, 2026112 ms
Aug 1, 2026113 ms
Aug 8, 2026115 ms
Aug 15, 2026116 ms
Aug 22, 2026115 ms
Aug 29, 2026113 ms
Sep 5, 2026112 ms
Sep 12, 2026113 ms
Sep 19, 2026113 ms
Sep 26, 2026114 ms
Oct 3, 2026118 ms
Oct 10, 2026120 ms
Oct 17, 2026121 ms
Oct 24, 2026124 ms
Oct 31, 2026117 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

Full-page screenshot of durex.com.ph (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. durex.com.ph at 0.4 s0.4 s
  2. durex.com.ph at 0.8 s0.8 s
  3. durex.com.ph at 1.1 s1.1 s
  4. durex.com.ph at 1.5 s1.5 s
  5. durex.com.ph at 1.9 s1.9 s
  6. durex.com.ph at 2.3 s2.3 s
  7. durex.com.ph at 2.6 s2.6 s
  8. durex.com.ph at 3.0 s3.0 s

Speed

2 to fix75
  • Reduce unused JavaScript

    900 ms · 486 KiB

    About 486 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 75

    75/100

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Optanon and contentstack.com), adding 567 KiB and 184 ms of main-thread time.

  • Improve image delivery

    193 KiB

    8 images could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 5 long tasks on the main thread

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

  • Use efficient cache lifetimes

    66 KiB

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

  • Reduce unused CSS

    61 KiB

    About 61 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 22 ms

    22 ms

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

Core Web Vitals

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

  • Time to Interactive: 11.7 s

    11.7 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

    The first text or image appears after 3.7 s on a phone. Good is under 1.8 s.

  • Speed Index: 6.7 s

    6.7 s

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

  • Real-user CLS: 0.16

    0.16

    For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 3.7 s

    3.7 s

    Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WARM UP YOUR NIGHTS...”. Most of its time is element render delay (2.3 s).

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 163 ms

    163 ms

    Real visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 691 ms

    691 ms

    Real visitors wait 691 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 135 ms

    135 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 70 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 70 requests on a phone: scripts 1,007 KiB (16), fonts 489 KiB (14) and other files 301 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.61 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 72.9 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

Google 100100
  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (19 characters)

    Your title is only 19 characters: “Homepage | Durex PH”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (17 characters)

    Your meta description is only 17 characters: “Durex Philippines”. 70 to 160 characters is enough to sell the click.

  • Structured data has 1 problem

    Structured data found (ItemList, Organization and WebPage) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://www.durex.com.ph/static/f1be4e47431de6ab27fe756cf326afff/blt1d6e6c14ebe…”.

  • 48 internal links, 1 external

    The homepage links to 48 pages on durex.com.ph and 1 external page.

5 checks passed
  • One H1 headline

    Your main headline reads: “WARM UP YOUR NIGHTS...”.

  • Canonical URL set

    The canonical URL is https://www.durex.com.ph/.

  • 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.durex.com.ph/sitemap.xml.

AI search readiness

1 to fix88
  • 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.durex.com.ph/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 (334 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix76
  • 15 pages without a title

    https://www.durex.com.ph/collections/all, https://www.durex.com.ph/collections/condoms, https://www.durex.com.ph/collections/condoms-basic-confidence, https://www.durex.com.ph/collections/condoms-feeling-and-intimacy, https://www.durex.com.ph/collections/condoms-fun-and-adventure and https://www.durex.com.ph/collections/condoms-performance and 9 others have no <title>, so Google invents the link text in results.

  • 15 pages without an H1

    https://www.durex.com.ph/collections/all, https://www.durex.com.ph/collections/condoms, https://www.durex.com.ph/collections/condoms-basic-confidence, https://www.durex.com.ph/collections/condoms-feeling-and-intimacy, https://www.durex.com.ph/collections/condoms-fun-and-adventure and https://www.durex.com.ph/collections/condoms-performance 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 33 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    18 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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 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 288 words of copy

    The homepage carries about 288 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop Now” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 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
  • 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 durex.com.ph, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
Gatsby
E-commerce
10 Shopify Products;Shopify;Shopify Plus
Analytics
Google Tag Manager
Hosting
Firebase Hosting

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on durex.com.ph, including 9 speed issues, 3 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