Website review, no card needed

biocare.de logo

biocare.de website review

Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 76 checks

This review found 34 issues worth fixing on biocare.de, 7 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of biocare.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. biocare.de at 0.6 s0.6 s
  2. biocare.de at 1.2 s1.2 s
  3. biocare.de at 1.8 s1.8 s
  4. biocare.de at 2.4 s2.4 s
  5. biocare.de at 3.0 s3.0 s
  6. biocare.de at 3.6 s3.6 s
  7. biocare.de at 4.2 s4.2 s
  8. biocare.de at 4.8 s4.8 s

Speed

6 to fix67
  • Render-blocking requests

    4.1 s

    23 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.1 s.

  • Mobile performance score: 67

    67/100

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

  • Font display

    950 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).

  • Reduce unused JavaScript

    640 ms · 138 KiB

    About 138 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 640 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 105 KiB

    About 105 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Main-thread work: 2.3 s

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 51 ms. During a long task the page ignores taps.

  • Improve image delivery

    20 KiB

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

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 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.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Adobe TypeKit), adding 24 KiB and 0 ms of main-thread time.

1 checks passed
  • Server response: 175 ms

    175 ms

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

Core Web Vitals

5 to fix71
  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Um dir ein optimales Erlebnis zu bieten, verwenden wir Tech…”. Most of its time is element render delay (2.9 s).

  • Speed Index: 6.7 s

    6.7 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

    The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 4.8 s

    4.8 s

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

  • Cumulative Layout Shift: 0.134

    0.134

    The layout shifts by 0.134 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 1 ms

    1 ms

    Scripts block the page for only 1 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 18.3 MB in 75 requests

    18.3 MB

    Your homepage downloads 18.3 MB in 75 requests on a phone: media 17.3 MB (2), scripts 372 KiB (22) and images 281 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • About 5.2 g of CO₂ per visit

    5.17 g

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

7 to fixGoogle 9393
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (22 elements)

    All page content should be contained by landmarks: 22 elements on the page fail this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 53 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: 53 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10083
  • Meta description is short (11 characters)

    Your meta description is only 11 characters: “Our mission”. 70 to 160 characters is enough to sell the click.

  • 4 H1 headlines

    There are 4 <h1> headlines (“TRICHOSAFE®”, “TRICHOCARE®” and “ATTRACAP®”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://biocare.de/sitemap.xml, so Google discovers your pages only by following links.

  • 55 internal links, 4 external

    The homepage links to 55 pages on biocare.de and 4 external pages.

4 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “Startseite BIOCARE 2025 - English - BIOCARE”.

  • Canonical URL set

    The canonical URL is https://biocare.de/language/en/.

  • Structured data in place

    Structured data found: Article, Organization, Person, Place and WebPage.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

    There is no https://biocare.de/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.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (913 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://biocare.de/language/en and / all use the title “Startseite BIOCARE 2025 - English - BIOCARE”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example /, whose canonical is https://biocare.de/language/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://biocare.de/contact-us, https://biocare.de/ansprechpartner-englisch and https://biocare.de/drone-pilot-training have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://biocare.de/trichosafe-englisch, https://biocare.de/trichocare-englisch, https://biocare.de/attracap-englisch, https://biocare.de/sitotroga-englisch, / and https://biocare.de/sitotroga took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 18 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.

  • 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.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9685
  • 7 small tap targets

    7 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address 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.

  • Thin social proof

    Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 590 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Retailer-Shop”, “Contact us” and “Your contact at Biocare”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 biocare.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Hosting
IONOS

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 biocare.de, including 11 speed issues, 4 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

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