Website review, no card needed

durex.co.uk logo

durex.co.uk website review

Visit site (opens in a new tab)Reviewed 23 October 202630 issues · 73 checks

This review found 30 issues worth fixing on durex.co.uk, 15 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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.8 s2.3 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.7 s
May 9, 20262.7 s
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
1.2 s898 msMay 2Oct 171.0 s
Show as table
DateReal-visitor tap response (INP)
May 2, 2026942 ms
May 9, 2026937 ms
May 16, 2026934 ms
May 23, 2026958 ms
May 30, 2026978 ms
Jun 6, 2026986 ms
Jun 13, 2026993 ms
Jun 20, 2026988 ms
Jun 27, 2026994 ms
Jul 4, 20261.0 s
Jul 11, 20261.1 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 2026993 ms
Oct 17, 20261.0 s

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.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. durex.co.uk at 0.6 s0.6 s
  2. durex.co.uk at 1.1 s1.1 s
  3. durex.co.uk at 1.7 s1.7 s
  4. durex.co.uk at 2.2 s2.2 s
  5. durex.co.uk at 2.8 s2.8 s
  6. durex.co.uk at 3.3 s3.3 s
  7. durex.co.uk at 3.9 s3.9 s
  8. durex.co.uk at 4.4 s4.4 s

Speed

8 to fix31
  • Reduce unused JavaScript

    2.7 s · 580 KiB

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

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 long tasks on the main thread

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

  • Improve image delivery

    669 KiB

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

  • 3 third-party services on the page

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

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Duplicated JavaScript

    350 ms · 23 KiB

    23 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 350 ms faster on a phone.

  • contentstack.com adds 0 ms

    0 ms

    contentstack.com costs a phone 0 ms of main-thread work and 1.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.

  • Use efficient cache lifetimes

    150 ms · 72 KiB

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

  • Reduce unused CSS

    71 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 59 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    9 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 35 ms

    35 ms

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

Core Web Vitals

12 to fix0
  • 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 LCP: 4.6 s

    4.6 s

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

  • Real-user INP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.37

    0.37

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 18.1 s

    18.1 s

    Your largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DUREX SILDENAFIL HELPS YOU GET HARD AND STAY HARD​ Availabl…”.

  • Time to Interactive: 20.1 s

    20.1 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 849 ms

    849 ms

    Scripts block taps and scrolling for 849 ms in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.273

    0.273

    The layout shifts by 0.273 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

Images and page weight

2 to fix75
  • Page weight: 3.8 MB in 88 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 88 requests on a phone: images 1.6 MB (34), scripts 1.1 MB (15) and other files 496 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    41 KiB

    1 image is downloaded at several times the size a phone draws it, for example Durex_Intensity_Optimised_Front_Pack_Visual_v2.png at 390 px wide, shown at 60 px. Resized copies would save about 41 KiB.

  • About 1.1 g of CO₂ per visit

    1.08 g

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

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

Accessibility

1 to fixGoogle 9899
  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 62 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

2 to fixGoogle 9293
  • Meta description is long (257 characters)

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

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

  • 71 internal links, 7 external

    The homepage links to 71 pages on durex.co.uk and 7 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “DUREX SILDENAFILHELPS YOUGET HARD AND STAY HARD​”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Condoms, Lubes, Massage Gels & Sex Toys | Durex UK”.

  • Canonical URL set

    The canonical URL is https://www.durex.co.uk/.

  • Structured data in place

    Structured data found: BreadcrumbList, ItemList, 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.durex.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, 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.co.uk/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 (448 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix76
  • 15 pages without a title

    https://www.durex.co.uk/collections/all-products, https://www.durex.co.uk/collections/condoms, https://www.durex.co.uk/collections/most-popular-condoms, https://www.durex.co.uk/collections/intensity-condoms, https://www.durex.co.uk/collections/nude-condoms and https://www.durex.co.uk/collections/thin-feel-condoms and 9 others have no <title>, so Google invents the link text in results.

  • 15 pages without an H1

    https://www.durex.co.uk/collections/all-products, https://www.durex.co.uk/collections/condoms, https://www.durex.co.uk/collections/most-popular-condoms, https://www.durex.co.uk/collections/intensity-condoms, https://www.durex.co.uk/collections/nude-condoms and https://www.durex.co.uk/collections/thin-feel-condoms 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 58 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
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 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 480 words of copy

    The homepage carries about 480 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: “LEARN MORE”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Learn more” 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.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 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.co.uk, 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
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on durex.co.uk, including 20 speed issues, 2 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