Website review, no card needed
femdisc.de website review
Visit site (opens in a new tab)Reviewed 6 November 202626 issues · 83 checks
This review found 26 issues worth fixing on femdisc.de, 9 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
84B- #21,590 of 120,337 reviewed websitesbeats 77%
- #13,998 of 68,137 online storesbeats 73%
- #13,581 of 62,092 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 865 ms |
| Jun 6, 2026 | 815 ms |
| Jun 13, 2026 | 778 ms |
| Jun 20, 2026 | 788 ms |
| Jun 27, 2026 | 801 ms |
| Jul 4, 2026 | 800 ms |
| Jul 11, 2026 | 804 ms |
| Jul 18, 2026 | 792 ms |
| Jul 25, 2026 | 779 ms |
| Aug 1, 2026 | 805 ms |
| Aug 8, 2026 | 836 ms |
| Aug 15, 2026 | 851 ms |
| Aug 22, 2026 | 877 ms |
| Aug 29, 2026 | 888 ms |
| Sep 5, 2026 | 896 ms |
| Sep 12, 2026 | 898 ms |
| Sep 19, 2026 | 870 ms |
| Sep 26, 2026 | 828 ms |
| Oct 3, 2026 | 768 ms |
| Oct 10, 2026 | 743 ms |
| Oct 17, 2026 | 720 ms |
| Oct 24, 2026 | 724 ms |
| Oct 31, 2026 | 709 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 153 ms |
| May 23, 2026 | 153 ms |
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 147 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 143 ms |
| Aug 8, 2026 | 145 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 147 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 150 ms |
| Sep 19, 2026 | 149 ms |
| Sep 26, 2026 | 148 ms |
| Oct 3, 2026 | 144 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 144 ms |
| Oct 24, 2026 | 143 ms |
| Oct 31, 2026 | 144 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
Render-blocking requests
1.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
2,085 HTML elements
The page has 2,085 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 43 KiB14 files are served with short cache lifetimes, so returning visitors download them again (43 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
34 KiB3 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (myshopify.com, JSDelivr CDN and Google Fonts and others), adding 198 KiB and 3 ms of main-thread time.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93. That is in Google's “good” band (90 and up).
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 58 ms of it running JavaScript. That is comfortably low.
Server response: 18 ms
18 msYour server sent the HTML in 18 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.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Γ”.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 153 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Real-user LCP: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 552 ms
552 msReal visitors wait 552 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 43% faster for real visitors
-43%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 2.6 s
2.6 sVisually, the page fills in at 2.6 s (Speed Index), inside the 3.4 s “good” threshold.
Time to Interactive: 2.6 s
2.6 sThe page is fully interactive after 2.6 s.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 28.2 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: 850 KiB in 118 requests
850 KiBYour homepage downloads 850 KiB in 118 requests on a phone: scripts 363 KiB (45), images 192 KiB (30) and HTML 134 KiB (2). 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
20 buttons without a name
20 buttons have no accessible name, so screen readers announce just “button”.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
24 images without alt text
24 images have no alt text, which hurts accessibility and image search.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (3 elements)
Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), 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. (1 element).
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “Warum Femdisc heraussticht”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("#")”.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
43 internal links, 7 external
The homepage links to 43 pages on femdisc.de and 7 external pages.
6 checks passed
Meta description: 84 characters
Your meta description is 84 characters: “Schützt vor Auslaufen über Nacht, beim Schwimmen und während des Geschlechtsverkehrs”.
Title: 46 characters
Your title is a healthy 46 characters: “femdisc wiederverwendbare Menstruationsscheibe”.
Canonical URL set
The canonical URL is https://femdisc.de/.
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://femdisc.de/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,634 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://femdisc.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://femdisc.de/collections/alleprodukte, https://femdisc.de/pages/faqs, https://femdisc.de/pages/how-to-use-v2, https://femdisc.de/products/femdisc-vaginal-probiotics, https://femdisc.de/collections/alle and https://femdisc.de/policies/legal-notice and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://femdisc.de/collections/alleprodukte, https://femdisc.de/apps/parcelpanel and https://femdisc.de/collections/alle 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 20 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
25 of 25 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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 876 words of copy
The homepage carries about 876 words of visible text.
3 checks passed
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
14 other companies contacted
Loading the homepage contacts 14 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 femdisc.de, 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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Aimerce First Party Pixel · Gorgias Live Chat Helpdesk · Uppromote Affiliate · Klaviyo Email Marketing Sms · Addingwell · Affliate By Secomapp · loox.io · linkster.co
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 | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on femdisc.de, including 7 speed issues, 3 SEO issues and 5 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.