Website review, no card needed
kvb.koeln website review
Visit site (opens in a new tab)Reviewed 29 October 202630 issues · 82 checks
This review found 30 issues worth fixing on kvb.koeln, 9 of them high impact, across 82 checks. The most urgent: render-blocking 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 926 ms |
| May 16, 2026 | 931 ms |
| May 23, 2026 | 964 ms |
| May 30, 2026 | 960 ms |
| Jun 6, 2026 | 970 ms |
| Jun 13, 2026 | 974 ms |
| Jun 20, 2026 | 938 ms |
| Jun 27, 2026 | 929 ms |
| Jul 4, 2026 | 928 ms |
| Jul 11, 2026 | 916 ms |
| Jul 18, 2026 | 912 ms |
| Jul 25, 2026 | 902 ms |
| Aug 1, 2026 | 871 ms |
| Aug 8, 2026 | 874 ms |
| Aug 15, 2026 | 808 ms |
| Aug 22, 2026 | 766 ms |
| Aug 29, 2026 | 795 ms |
| Sep 5, 2026 | 798 ms |
| Sep 12, 2026 | 822 ms |
| Sep 19, 2026 | 820 ms |
| Sep 26, 2026 | 822 ms |
| Oct 3, 2026 | 859 ms |
| Oct 10, 2026 | 891 ms |
| Oct 17, 2026 | 945 ms |
| Oct 24, 2026 | 916 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 121 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 117 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 117 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 115 ms |
| Jun 27, 2026 | 115 ms |
| Jul 4, 2026 | 116 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 106 ms |
| Aug 29, 2026 | 109 ms |
| Sep 5, 2026 | 117 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 143 ms |
| Oct 3, 2026 | 131 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 130 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
Render-blocking requests
3.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Font display
800 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).
Use efficient cache lifetimes
150 ms · 287 KiB43 files are served with short cache lifetimes, so returning visitors download them again (287 KiB).
eye-able.com adds 130 ms
130 mseye-able.com costs a phone 130 ms of main-thread work and 415 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 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 217 ms. During a long task the page ignores taps.
Reduce unused JavaScript
210 KiBAbout 210 KiB of JavaScript is downloaded but never used on this page.
1 third-party service on the page
1 third-party service load with your homepage (eye-able.com), adding 415 KiB and 130 ms of main-thread time.
Improve image delivery
105 KiB9 images could be 105 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 372 ms of it running JavaScript. That is comfortably low.
Server response: 111 ms
111 msYour server sent the HTML in 111 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 14.6 s
14.6 sThe page becomes fully interactive after 14.6 s. Good is under 3.8 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.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.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Demonstration im Innenstadtbereich am 31.10.26 Wegen einer …”. Most of its time is element render delay (2.3 s).
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 121 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 328 ms
328 msReal visitors wait 328 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 159 ms
159 msScripts block the page for only 159 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.075
0.075The layout barely moves while loading (CLS 0.075, good is under 0.1).
Images and page weight
2 images over 500 KB
2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.
Page weight: 3.5 MB in 82 requests
3.5 MBYour homepage downloads 3.5 MB in 82 requests on a phone: images 2.3 MB (33), scripts 923 KiB (34) and other files 111 KiB (9). Under 2 MB keeps phones on slow connections fast.
10 images in older formats
10 images (2.2 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.
9 images below the first screen load straight away
9 images further down the page (406 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 34 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 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (27 characters)
Your title is only 27 characters: “Kölner Verkehrs-Betriebe AG”. Between 30 and 65 characters leaves room to say what you do and for whom.
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://kvb.koeln/sitemap.xml, so Google discovers your pages only by following links.
10 links crawlers can't follow
10 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
92 internal links, 15 external
The homepage links to 92 pages on kvb.koeln and 15 external pages.
3 checks passed
One H1 headline
Your main headline reads: “KVB - Kölner Verkehrs-Betriebe AG”.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place.
AI search readiness
No llms.txt
There is no https://kvb.koeln/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: 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 (555 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://kvb.koeln/mobilitaet/index.html all use the title “Kölner Verkehrs-Betriebe AG”. 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://kvb.koeln/mobilitaet/index.html has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 73 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.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'settings')”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
80 of 88 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.
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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 361 words of copy
The homepage carries about 361 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “KVB-Shop”.
3 short forms
3 short forms (6 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 cookies set on arrival
2Opening 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.
1 other company contacted
Loading the homepage contacts 1 host 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 kvb.koeln, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics
- Hosting
- Netcologne
Company
- Founded
- 1876
- Headquarters
- Cologne
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on kvb.koeln, including 10 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.