Website review, no card needed
seniorreha.de website review
Visit site (opens in a new tab)Reviewed 12 November 202635 issues · 79 checks
This review found 35 issues worth fixing on seniorreha.de, 9 of them high impact, across 79 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
76C- #71,944 of 117,690 reviewed websitesbeats 34%
- #46,461 of 66,925 online storesbeats 26%
- #44,078 of 61,020 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 121 ms |
| May 30, 2026 | 123 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 131 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 133 ms |
| Jul 4, 2026 | 130 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 123 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 135 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 134 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 211 ms |
| Oct 17, 2026 | 221 ms |
| Oct 24, 2026 | 228 ms |
| Oct 31, 2026 | 235 ms |
| Nov 7, 2026 | 236 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
1.9 s · 311 KiBAbout 311 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Improve image delivery
258 KiB10 images could be 258 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,490 HTML elements
The page has 2,490 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 130 ms
130 msShopify costs a phone 130 ms of main-thread work and 571 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.
4 third-party services on the page
4 third-party services load with your homepage (Shopify, Google Fonts and consentmo.com and others), adding 682 KiB and 130 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
Reduce unused CSS
29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
Use efficient cache lifetimes
1 KiB1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 527 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 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.50
0.50For real visitors the layout shifts by 0.50 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BLACK FRIDAY Banner mit Rollstuhl, Duschhocker, Kosmetiktas…”.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Real-user INP: 229 ms
229 msReal visitors wait 229 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 93% slower for real visitors
+93%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 121 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
6 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 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: 604 ms
604 msReal visitors wait 604 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 52 ms
52 msScripts block the page for only 52 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.9 MB in 252 requests
2.9 MBYour homepage downloads 2.9 MB in 252 requests on a phone: other files 1.0 MB (149), scripts 801 KiB (51) and images 769 KiB (25). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Forsidebanner_LEVERING-TIL-DOEREN_3200x2134_d9279b1e-7c14-4f is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.8 g of CO₂ per visit
0.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 76 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is an empty list”.
357 internal links, 0 external
The homepage links to 357 pages on seniorreha.de and 0 external pages.
7 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Seniorreha bietet über 2000 e – von Rollatoren und Gehstöcken bis hin zu Kompressionsstrümpfen und Pillendosen. Besuche…”.
One H1 headline
Your main headline reads: “Große Auswahl an Hilfsmitteln für Senioren”.
Title: 42 characters
Your title is a healthy 42 characters: “Seniorreha - Größe Auswahl an Hilfsmitteln”.
Canonical URL set
The canonical URL is https://seniorreha.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://seniorreha.de/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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.
3 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 (1,739 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://seniorreha.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://seniorreha.de/customer_authentication/redirect has no <title>, so Google invents the link text in results.
3 linked pages hidden from search
https://seniorreha.de/pages/1-3-tage-lieferung, https://seniorreha.de/pages/wer-ist-seniorreha and https://seniorreha.de/customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
https://seniorreha.de/pages/rucksendungen and https://seniorreha.de/pages/sadan-returnerer-du all use the title “So retournieren Sie einen Artikel - Seniorshop”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://seniorreha.de/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://seniorreha.de/pages/rucksendungen and https://seniorreha.de/pages/sadan-returnerer-du use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://seniorreha.de/pages/sadan-returnerer-du, whose canonical is https://seniorreha.de/pages/rucksendungen. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://seniorreha.de/customer_authentication/redirect has 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 198 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot redefine property: cookie”.
2 checks passed
Tap targets are thumb-sized
52 of 57 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 1,107 words of copy
The homepage carries about 1,107 words of visible text.
3 checks passed
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 19 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
17 other companies contacted
Loading the homepage contacts 17 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 seniorreha.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Gdpr Backpack · Stape Remix · Forms · Restockrocket · Free Contact Form · Qikify
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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on seniorreha.de, including 14 speed issues, 1 SEO issue and 3 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.