Website review, no card needed

durex.at logo

durex.at website review

Visit site (opens in a new tab)Reviewed 9 November 202619 issues · 70 checks

This review found 19 issues worth fixing on durex.at, 7 of them high impact, across 70 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
1.9 s1.5 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
130 ms111 msMay 23Nov 7118 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026128 ms
May 30, 2026128 ms
Jun 6, 2026114 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026113 ms
Jul 4, 2026119 ms
Jul 11, 2026123 ms
Jul 18, 2026122 ms
Jul 25, 2026121 ms
Aug 1, 2026126 ms
Aug 8, 2026125 ms
Aug 15, 2026122 ms
Aug 22, 2026122 ms
Aug 29, 2026114 ms
Sep 5, 2026116 ms
Sep 12, 2026118 ms
Sep 19, 2026119 ms
Sep 26, 2026119 ms
Oct 3, 2026117 ms
Oct 10, 2026121 ms
Oct 17, 2026119 ms
Oct 24, 2026121 ms
Oct 31, 2026119 ms
Nov 7, 2026118 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.at (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix85
  • Mobile performance score: 85

    85/100

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

  • Reduce unused JavaScript

    754 KiB

    About 754 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    405 KiB

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

  • Main-thread work: 2.6 s

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

  • contentstack.com adds 0 ms

    0 ms

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

  • 3 third-party services on the page

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

  • 11 long tasks on the main thread

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

  • Use efficient cache lifetimes

    70 KiB

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

  • Reduce unused CSS

    62 KiB

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

  • Duplicated JavaScript

    21 KiB

    21 KiB JavaScript is shipped twice across bundles.

  • 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: 16 ms

    16 ms

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

Core Web Vitals

5 to fix50
  • 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.40

    0.40

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

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Total Blocking Time: 342 ms

    342 ms

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

  • 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 128 ms to 118 ms 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-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 680 ms

    680 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 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).

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Die Reckitt Benckiser Austria GmbH verwendet notwendige Coo…”.

Images and page weight

2 to fix75
  • Page weight: 2.7 MB in 76 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 76 requests on a phone: scripts 1.3 MB (17), images 493 KiB (23) and fonts 489 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    55 KiB

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

  • About 0.8 g of CO₂ per visit

    0.76 g

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

Google 98100
  • Headings skip levels

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

  • 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 53 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 65 internal links, 3 external

    The homepage links to 65 pages on durex.at and 3 external pages.

8 checks passed
  • Meta description: 91 characters

    Your meta description is 91 characters: “Erlebe intensive Gefühle - mit den Produkten von Durex. Gleitgele · Kondome · Sexspielzeuge”.

  • One H1 headline

    Your main headline reads: “ERLEBE​ INTENSIVE​ GEFÜHLE MIT​ DUREX”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Durex AT - Kondome, Gleitgele und Spielzeuge | Durex AT”.

  • Canonical URL set

    The canonical URL is https://durex.at/.

  • 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://durex.at/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.at/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 (526 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix76
  • 15 pages without a title

    https://www.durex.at/collections/alle-produkte, https://www.durex.at/collections/alle-kondome, https://www.durex.at/collections/dunne-und-ultra-dunne-kondome, https://www.durex.at/collections/hautnah-kondome, https://www.durex.at/collections/intensity and https://www.durex.at/collections/performance and 9 others have no <title>, so Google invents the link text in results.

  • 15 pages without an H1

    https://www.durex.at/collections/alle-produkte, https://www.durex.at/collections/alle-kondome, https://www.durex.at/collections/dunne-und-ultra-dunne-kondome, https://www.durex.at/collections/hautnah-kondome, https://www.durex.at/collections/intensity and https://www.durex.at/collections/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 44 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 628 words of copy

    The homepage carries about 628 words of visible text.

1 checks passed
  • 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.at, 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 19 issues on durex.at, including 10 speed 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

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