Website review, no card needed
bellevue.de website review
Visit site (opens in a new tab)Reviewed 28 October 202638 issues · 80 checks
This review found 38 issues worth fixing on bellevue.de, 14 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 146 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 141 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 139 ms |
| Aug 29, 2026 | 142 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 156 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 153 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
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.1 s
4.7 s
Speed
Use efficient cache lifetimes
2.9 s · 6.6 MB56 files are served with short cache lifetimes, so returning visitors download them again (6.6 MB).
Render-blocking requests
2.1 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Improve image delivery
550 ms · 2.7 MB18 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Reduce unused JavaScript
600 ms · 543 KiBAbout 543 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, consentmanager.net and Google Analytics and others), adding 839 KiB and 722 ms of main-thread time.
Google Tag Manager adds 507 ms
507 msGoogle Tag Manager costs a phone 507 ms of main-thread work and 673 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
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
Reduce unused CSS
300 ms · 44 KiBAbout 44 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 192 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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 880 ms of it running JavaScript. That is comfortably low.
Server response: 125 ms
125 msYour server sent the HTML in 125 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.
Time to Interactive: 12.5 s
12.5 sThe page becomes fully interactive after 12.5 s. Good is under 3.8 s.
Speed Index: 8.4 s
8.4 sVisually, the page fills in at 8.4 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.3 s
4.3 sYour largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Haus mit Pool auf der Terrasse”.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 954 ms
954 msReal visitors wait 954 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 258 ms
258 msScripts block taps and scrolling for 258 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 145 ms
145 msReal visitors wait 145 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.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 7.4 MB in 72 requests
7.4 MBYour homepage downloads 7.4 MB in 72 requests on a phone: images 5.9 MB (37), scripts 1.2 MB (16) and fonts 191 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
csm_Berlin_Story__81014e8597.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.
24 images far larger than shown
1.7 MB24 images are downloaded at several times the size a phone draws them, for example csm_Berlin_Story__81014e8597.png at 1,200 px wide, shown at 350 px. Resized copies would save about 1.7 MB.
33 images in older formats
33 images (5.9 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.
31 images below the first screen load straight away
31 images further down the page (5.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.09 g of CO₂e: 250.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
autocomplete attribute must be used correctly (1 element)
autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 33 images in the HTML carry an alt attribute.
48 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: 48 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Besondere Immobilien - Luxusimmobilien kaufen oder mieten - Bellevue”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
110 internal links, 18 external
The homepage links to 110 pages on bellevue.de and 18 external pages.
5 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Finden Sie Ihre besondere Immobilie und Luxusimmobilie: Luxushäuser, Villen, Landhäuser jeder Art, erstklassigen Wohnun…”.
One H1 headline
Your main headline reads: “DIE SCHÖNSTEN IMMOBILIEN WELTWEIT”.
Canonical URL set
The canonical URL is https://www.bellevue.de/.
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://www.bellevue.de/sitemap.xml.
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://www.bellevue.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
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,301 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.bellevue.de/immobiliensuche/merkzettel.html and https://www.bellevue.de/suche.html are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without an H1
https://www.bellevue.de/kontakt.html and https://www.bellevue.de/immobilien-anbieten/best-property-agents.html have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.bellevue.de/immobilien-anbieten/best-property-agents.html took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 59 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 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 a title
All 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 12 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 “The method 'deanonymizeUser' was not found in "_paq" variable. Please have a look at the Matomo tracker documentation: …”.
Pasting is blocked
A form field blocks pasting, which frustrates password managers and people on phones.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
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 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,158 words of copy
The homepage carries about 1,158 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Shop”.
2 short forms
2 short forms (4 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (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: consentmanager
A consent management tool (consentmanager) 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 bellevue.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
- TYPO3 CMS
- Analytics
- Google Tag Manager
- Hosting
- Hetzner
Company
- Founded
- 1990
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bellevue.de, including 17 speed issues, 2 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.