Website review, no card needed
durex.pl website review
Visit site (opens in a new tab)Reviewed 9 November 202624 issues · 71 checks
This review found 24 issues worth fixing on durex.pl, 13 of them high impact, across 71 checks. The most urgent: reduce unused JavaScript. 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
64D- #111,357 of 118,391 reviewed websitesbeats 5%
- #65,415 of 67,267 online storesbeats 2%
- #59,971 of 61,337 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 335 ms |
| May 30, 2026 | 345 ms |
| Jun 6, 2026 | 344 ms |
| Jun 13, 2026 | 339 ms |
| Jun 20, 2026 | 344 ms |
| Jun 27, 2026 | 340 ms |
| Jul 4, 2026 | 342 ms |
| Jul 11, 2026 | 340 ms |
| Jul 18, 2026 | 345 ms |
| Jul 25, 2026 | 342 ms |
| Aug 1, 2026 | 338 ms |
| Aug 8, 2026 | 341 ms |
| Aug 15, 2026 | 335 ms |
| Aug 22, 2026 | 331 ms |
| Aug 29, 2026 | 329 ms |
| Sep 5, 2026 | 327 ms |
| Sep 12, 2026 | 313 ms |
| Sep 19, 2026 | 306 ms |
| Sep 26, 2026 | 302 ms |
| Oct 3, 2026 | 295 ms |
| Oct 10, 2026 | 298 ms |
| Oct 17, 2026 | 304 ms |
| Oct 24, 2026 | 308 ms |
| Oct 31, 2026 | 309 ms |
| Nov 7, 2026 | 305 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
Speed
Reduce unused JavaScript
2.7 s · 741 KiBAbout 741 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: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 707 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
350 ms · 65 KiB5 files are served with short cache lifetimes, so returning visitors download them again (65 KiB).
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Optanon and contentstack.com), adding 537 KiB and 195 ms of main-thread time.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
91 KiB5 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
60 KiBAbout 60 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
21 KiB21 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.37
0.37For real visitors the layout shifts by 0.37 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 13.8 s
13.8 sYour largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “My, Reckitt Benckiser (Poland) S.A., używamy niezbędnych pl…”.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 14.0 s
14.0 sThe page becomes fully interactive after 14.0 s. Good is under 3.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.273
0.273The layout shifts by 0.273 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 479 ms
479 msReal visitors wait 479 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 499 ms
499 msReal visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 335 ms to 305 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.4 MB in 68 requests
2.4 MBYour homepage downloads 2.4 MB in 68 requests on a phone: scripts 1.3 MB (19), fonts 489 KiB (14) and other files 393 KiB (21). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 81.0 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
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.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail 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 35 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
73 internal links, 2 external
The homepage links to 73 pages on durex.pl and 2 external pages.
8 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Sprawdź nasze produkty i specjalne zestawy, które dla Ciebie przygotowaliśmy. Produkty Durex bezpośrednio od producenta…”.
One H1 headline
Your main headline reads: “DLA NAJWIĘKSZEJ INTENSYWNOŚCI DOZNAŃ”.
Title: 62 characters
Your title is a healthy 62 characters: “Oficjalny sklep marki Durex.pl | Zestaw Mystery Box | Durex PL”.
Canonical URL set
The canonical URL is https://www.durex.pl/.
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.pl/sitemap.xml.
AI search readiness
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.pl/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 (534 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a title
https://www.durex.pl/collections/wszystkie-produkty, https://www.durex.pl/collections/prezerwatywy, https://www.durex.pl/collections/nowa-generacja, https://www.durex.pl/collections/cienkie-i-super, https://www.durex.pl/collections/prezerwatywy-dla-dluzszej-przyjemnosci and https://www.durex.pl/collections/prezerwatywy-prazkowane-i-z-wypustkami and 9 others have no <title>, so Google invents the link text in results.
15 pages without an H1
https://www.durex.pl/collections/wszystkie-produkty, https://www.durex.pl/collections/prezerwatywy, https://www.durex.pl/collections/nowa-generacja, https://www.durex.pl/collections/cienkie-i-super, https://www.durex.pl/collections/prezerwatywy-dla-dluzszej-przyjemnosci and https://www.durex.pl/collections/prezerwatywy-prazkowane-i-z-wypustkami and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages slow to respond
https://www.durex.pl/collections/klasyczne, https://www.durex.pl/collections/prezerwatywy-nielateksowe, https://www.durex.pl/collections/zele-intymne, https://www.durex.pl/collections/zele-intymne-na-bazie-wody, https://www.durex.pl/collections/zele-intymne-naturals and https://www.durex.pl/collections/silikonowe-zele-intymne and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
15 of 15 tappable elements near the top are at least 24 px.
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.
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.
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 445 words of copy
The homepage carries about 445 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before 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.pl, 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
- 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 24 issues on durex.pl, including 14 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.