Website review, no card needed

paracelsus.com logo

paracelsus.com website review

Visit site (opens in a new tab)Reviewed 24 October 202625 issues · 79 checks

This review found 25 issues worth fixing on paracelsus.com, 6 of them high impact, across 79 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

Real-visitor load time (LCP)75th percentile, phones
1.7 s990 msMay 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.5 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.6 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.2 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
132 ms100 msMay 2Oct 17115 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026110 ms
May 9, 2026116 ms
May 16, 2026117 ms
May 23, 2026110 ms
May 30, 2026104 ms
Jun 6, 2026104 ms
Jun 13, 2026106 ms
Jun 20, 2026108 ms
Jul 4, 2026113 ms
Jul 11, 2026119 ms
Jul 18, 2026120 ms
Jul 25, 2026123 ms
Aug 1, 2026118 ms
Aug 15, 2026118 ms
Aug 22, 2026114 ms
Aug 29, 2026113 ms
Sep 5, 2026109 ms
Sep 12, 2026111 ms
Sep 19, 2026119 ms
Sep 26, 2026128 ms
Oct 3, 2026124 ms
Oct 10, 2026121 ms
Oct 17, 2026115 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

Full-page screenshot of paracelsus.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. paracelsus.com at 0.4 s0.4 s
  2. paracelsus.com at 0.8 s0.8 s
  3. paracelsus.com at 1.1 s1.1 s
  4. paracelsus.com at 1.5 s1.5 s
  5. paracelsus.com at 1.9 s1.9 s
  6. paracelsus.com at 2.3 s2.3 s
  7. paracelsus.com at 2.6 s2.6 s
  8. paracelsus.com at 3.0 s3.0 s

Speed

5 to fix80
  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 80

    80/100

    Your mobile performance score is 80 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    250 ms · 630 KiB

    5 images could be 630 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Font display

    800 ms

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

  • 1,601 HTML elements

    The page has 1,601 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused JavaScript

    100 ms · 133 KiB

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

  • Reduce unused CSS

    150 ms · 23 KiB

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

  • 1 long task on the main thread

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

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 45 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 373 ms of it running JavaScript. That is comfortably low.

  • Server response: 122 ms

    122 ms

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

Core Web Vitals

6 to fix100
  • 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 TTFB: 853 ms

    853 ms

    Real visitors wait 853 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Biologische Medizin Wenn Medizin einen Schritt weiter geht.…”.

  • Speed Index: 5.1 s

    5.1 s

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

  • 7 images without width and height

    7 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 110 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

    Real visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 112 ms

    112 ms

    Real visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Largest content (LCP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.095

    0.095

    The layout barely moves while loading (CLS 0.095, good is under 0.1).

  • Time to Interactive: 3.6 s

    3.6 s

    The page is fully interactive after 3.6 s.

  • Total Blocking Time: 3 ms

    3 ms

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

Images and page weight

2 to fix80
  • 3 images in older formats

    3 images (753 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 3 images far larger than shown

    109 KiB

    3 images are downloaded at several times the size a phone draws them, for example old-paracelsus01.jpg at 1,200 px wide, shown at 370 px. Resized copies would save about 109 KiB.

  • About 0.5 g of CO₂ per visit

    0.52 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.52 g of CO₂e: 62.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Page weight: 1.8 MB in 83 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 83 requests on a phone: images 1.1 MB (12), scripts 326 KiB (29) and fonts 305 KiB (8). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 9394
  • 46 text elements with low contrast

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

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

    Contentinfo 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 contentinfo landmark (1 element)

    Document should not have more than one contentinfo 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.

  • 7 links without text

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3 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. (5 elements).

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • 2 H1 headlines

    There are 2 <h1> headlines (“Biologische Medizin” and “Herzlich Willkommen in der Paracelsus Klinik für …”). One clear main headline is easier for people and search engines.

  • 167 internal links, 6 external

    The homepage links to 167 pages on paracelsus.com and 6 external pages.

7 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Erfahrenste Klinik für ganzheitliche biologische Medizin. Wir behandeln Ursachen statt Symptome in einer ganzheitlichen…”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Paracelsus Clinic für Biologische Medizin”.

  • Canonical URL set

    The canonical URL is https://paracelsus.com/.

  • Structured data in place

    Structured data found: Article, BlogPosting, BreadcrumbList, ImageObject and Organization.

  • 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://paracelsus.com/sitemap_index.xml.

AI search readiness

100
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: 6 of 6 facts

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

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

  • llms.txt published

    The site publishes https://paracelsus.com/llms.txt (2 KiB, 26 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 9693
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (7 required). Every extra field lowers completion.

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

    The homepage carries about 595 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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 paracelsus.com, 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
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on paracelsus.com, including 11 speed issues, 1 SEO issue 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

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