Website review, no card needed
baldriparan.de website review
Visit site (opens in a new tab)Reviewed 17 November 202634 issues · 73 checks
This review found 34 issues worth fixing on baldriparan.de, 11 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77C- #65,764 of 117,376 reviewed websitesbeats 39%
- #42,959 of 66,897 online storesbeats 31%
- #40,913 of 61,005 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.4 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 140 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 144 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 141 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 157 ms |
| Oct 3, 2026 | 175 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 195 ms |
| Oct 31, 2026 | 193 ms |
| Nov 7, 2026 | 190 ms |
| Nov 14, 2026 | 194 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.1 s · 456 KiBAbout 456 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
1.1 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
300 ms · 1.1 MB20 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 63
63/100Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
500 ms · 121 KiB16 files are served with short cache lifetimes, so returning visitors download them again (121 KiB).
8 third-party services on the page
8 third-party services load with your homepage (jQuery CDN, Klaviyo and Google Tag Manager and others), adding 1.1 MB and 460 ms of main-thread time.
Legacy JavaScript
450 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
300 ms · 36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,110 HTML elements
The page has 2,110 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 838 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Klaviyo adds 106 ms
106 msKlaviyo costs a phone 106 ms of main-thread work and 340 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Largest Contentful Paint: 16.9 s
16.9 sYour largest element takes 16.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bekannt aus dem TV - Baldriparan Magnesium+ – Premiumkomple…”.
Time to Interactive: 17.3 s
17.3 sThe page becomes fully interactive after 17.3 s. Good is under 3.8 s.
Speed Index: 7.6 s
7.6 sVisually, the page fills in at 7.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 39% slower for real visitors
+39%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 138 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 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 content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
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: 560 ms
560 msReal visitors wait 560 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 38 ms
38 msScripts block the page for only 38 ms while loading. Good is under 200 ms.
Images and page weight
9 images far larger than shown
549 KiB9 images are downloaded at several times the size a phone draws them, for example 250902_BPN_Monoshop_Rezensionen_V001_phw.jpg at 1,200 px wide, shown at 280 px. Resized copies would save about 549 KiB.
Page weight: 4.0 MB in 277 requests
4.0 MBYour homepage downloads 4.0 MB in 277 requests on a phone: images 1.6 MB (42), scripts 1.2 MB (84) and other files 868 KiB (124). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Logo_BP-INT_weiss.png 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).
8 images below the first screen load straight away
8 images further down the page (777 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 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 (“Baldriparan” and “Baldriparan – für gesunden Schlaf und einen guten…”). One clear main headline is easier for people and search engines.
73 internal links, 2 external
The homepage links to 73 pages on baldriparan.de and 2 external pages.
7 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Entdecke Baldriparan® – pflanzliche Hilfe bei innerer Unruhe und Schlafstörungen. Direkt von Hersteller im offiziellen …”.
Title: 63 characters
Your title is a healthy 63 characters: “Baldriparan® – Sanfte Unterstützung bei innerer Unruhe & Schlaf”.
Canonical URL set
The canonical URL is https://baldriparan.de/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://baldriparan.de/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing 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.
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,400 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://baldriparan.de/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 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
10 small tap targets
10 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'open' of object '#<Window>'”.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
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 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 2,183 words of copy
The homepage carries about 2,183 words of visible text.
4 checks passed
4 short forms
4 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and 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.
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 2 of them by other companies (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.
26 other companies contacted
Loading the homepage contacts 26 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 baldriparan.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
Pandectes Gdpr · Kameleoon A B Testing · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Gdpr Cookie Consent · Reviews Co Uk Product And Merchant Review Collection · trustedshops.com
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 Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on baldriparan.de, including 19 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.