Website review, no card needed
kliniken-koeln.de website review
Visit site (opens in a new tab)Reviewed 19 November 202648 issues · 90 checks
This review found 48 issues worth fixing on kliniken-koeln.de, 17 of them high impact, across 90 checks. The most urgent: page weight: 21.3 MB in 69 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jul 18, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.4 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.7 s |
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
How it loaded on a phone
0.7 s
1.5 s
2.2 s
3.0 s
3.7 s
4.5 s
5.2 s
6.0 s
Speed
3,805 HTML elements
The page has 3,805 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
20.0 MB58 files are served with short cache lifetimes, so returning visitors download them again (20.0 MB).
Improve image delivery
3.4 MB9 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Document request latency
950 ms · 637 KiBThe HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Reduce initial server response time
929 msReduce initial server response time. Google estimates savings of 929 ms on a phone.
Font display
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
Render-blocking requests
850 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Server response: 1.0 s
1.0 sYour server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
3 third-party services on the page
3 third-party services load with your homepage (Cookiebot, Google Tag Manager and conword.io), adding 357 KiB and 288 ms of main-thread time.
Reduce unused JavaScript
205 KiBAbout 205 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 83 ms. During a long task the page ignores taps.
Reduce unused CSS
24 KiBAbout 24 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
9 KiB9 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.
1 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 341 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden Cookies, um Inhalte und Anzeigen zu personali…”. Most of its time is element render delay (4.2 s).
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.3 s
9.3 sThe page becomes fully interactive after 9.3 s. Good is under 3.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 61 ms
61 msScripts block the page for only 61 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 21.3 MB in 69 requests
21.3 MBYour homepage downloads 21.3 MB in 69 requests on a phone: images 19.6 MB (25), HTML 952 KiB (2) and scripts 619 KiB (33). Under 2 MB keeps phones on slow connections fast.
9 images over 500 KB
9 images weigh 19.1 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
7.0 MB5 images are downloaded at several times the size a phone draws them, for example 1963_1_keyvisual_web_Gesundheitscampus_Merheim_Vogelperspekt at 1,920 px wide, shown at 390 px. Resized copies would save about 7.0 MB.
18 images in older formats
18 images (19.6 MB) 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.
7 images below the first screen load straight away
7 images further down the page (996 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.0 g of CO₂ per visit
6.03 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.03 g of CO₂e: 723.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
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.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
44 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: 44 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://kliniken-koeln.de/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at kliniken-koeln.de/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1,152 internal links, 7 external
The homepage links to 1,152 pages on kliniken-koeln.de and 7 external pages.
2 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Herzlich willkommen bei den Kliniken der Stadt Köln (Kinderkrankenhaus Amsterdamer Straße, Krankenhaus Holweide, Kranke…”.
Title: 52 characters
Your title is a healthy 52 characters: “Kliniken Köln - Merheim, Holweide, Kinderkrankenhaus”.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://kliniken-koeln.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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (3,449 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://kliniken-koeln.de/Ueber_uns_index.htm, https://kliniken-koeln.de/Allgemeines_Kontaktformular_ICON.htm, https://kliniken-koeln.de/Spenden.htm and https://kliniken-koeln.de/Kinderkrankenhaus_F_Trakt.htm have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://kliniken-koeln.de/Kinderanaesthesiologie_Startseite.htm, https://kliniken-koeln.de/Kinderanaesthesiologie_Narkosevorgespraech.htm, https://kliniken-koeln.de/Kinderanaesthesiologie_Narkosegespraech__Sprechzeiten.htm, https://kliniken-koeln.de/Kinderanaesthesiologie_Anaesthesieverfahren.htm, https://kliniken-koeln.de/Kinderanaesthesiologie_Aufwachraum.htm and https://kliniken-koeln.de/Kinderanaesthesiologie_Schmerztherapie.htm and 2 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://kliniken-koeln.de/Ueber_uns_index.htm, https://kliniken-koeln.de/Allgemeines_Kontaktformular_ICON.htm, https://kliniken-koeln.de/Spenden.htm, https://kliniken-koeln.de/Service_Presse_Startseite.htm, https://kliniken-koeln.de/Mensch_und_Medizin.htm and https://kliniken-koeln.de/Kinderkrankenhaus_Index.htm and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://kliniken-koeln.de/Allgemeines_Kontaktformular_ICON.htm, https://kliniken-koeln.de/Spenden.htm, https://kliniken-koeln.de/Service_Presse_Startseite.htm, https://kliniken-koeln.de/Kinderkrankenhaus_Index.htm and https://kliniken-koeln.de/Kinderanaesthesiologie_Startseite.htm took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
5 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.
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 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 30 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_SSL_UNRECOGNIZED_NAME_ALERT”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 1,042 words of copy
The homepage carries about 1,042 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Download”.
1 short form
A short form (5 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 kliniken-koeln.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on kliniken-koeln.de, including 14 speed issues, 7 SEO issues 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.