Website review, no card needed
nabu.de website review
Visit site (opens in a new tab)Reviewed 28 October 202634 issues · 69 checks
This review found 34 issues worth fixing on nabu.de, 9 of them high impact, across 69 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
71CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
1.6 s · 1.1 MB26 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
hcaptcha.com adds 2.1 s
2.1 shcaptcha.com costs a phone 2.1 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 4.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5 third-party services on the page
5 third-party services load with your homepage (hcaptcha.com, Stripe and fundraisingbox.com and others), adding 3.2 MB and 3.4 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 62). Pages that score under 90 lose visitors before the first paint.
Stripe adds 770 ms
770 msStripe costs a phone 770 ms of main-thread work and 590 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.
Reduce unused JavaScript
310 ms · 474 KiBAbout 474 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.
Improve image delivery
500 ms · 73 KiB2 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Render-blocking requests
500 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 442 ms. During a long task the page ignores taps.
fundraisingbox.com adds 379 ms
379 msfundraisingbox.com costs a phone 379 ms of main-thread work and 246 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.
Other Google APIs/SDKs adds 19 ms
19 msOther Google APIs/SDKs costs a phone 19 ms of main-thread work and 435 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.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 46.5 s
46.5 sThe page becomes fully interactive after 46.5 s. Good is under 3.8 s.
Speed Index: 12.0 s
12.0 sVisually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 3.3 s
3.3 sYour largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “aktuell gibt es weltweit eine kritische Sicherheitslücke in…”. Most of its time is element render delay (1.4 s).
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
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
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.4 MB in 157 requests
7.4 MBYour homepage downloads 7.4 MB in 157 requests on a phone: scripts 5.8 MB (49), other files 763 KiB (70) and HTML 496 KiB (19). Under 2 MB keeps phones on slow connections fast.
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: 251.2 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
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 0 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.
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://nabu.de/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at nabu.de/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
10 internal links, 4 external
The homepage links to 10 pages on nabu.de and 4 external pages.
2 checks passed
One H1 headline
Your main headline reads: “Wir sind weiterhin für Sie da”.
Title: 37 characters
Your title is a healthy 37 characters: “Wir sind die Naturschutzmacher*innen!”.
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://nabu.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (778 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a title
https://nabu.de/index.html, https://nabu.de/mitgliedschaft.html, https://nabu.de/patenschaft.html, https://nabu.de/impressum.html and https://nabu.de/datenschutz/index.html all use the title “Wir sind die Naturschutzmacher*innen!”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://nabu.de/mitgliedschaft.html, https://nabu.de/patenschaft.html, https://nabu.de/impressum.html and https://nabu.de/datenschutz/index.html have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://nabu.de/mitgliedschaft.html, https://nabu.de/patenschaft.html and https://nabu.de/impressum.html have no <h1> headline, so visitors and search engines get no clear main topic.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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
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.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 771 words of copy
The homepage carries about 771 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Shop”.
Direct contact links
Visitors can reach you directly: 27 phone links and 28 email links.
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.
15 other companies contacted
Loading the homepage contacts 15 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 nabu.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- Hosting
- Frankfurt-Munich-Stuttgart-Amsterdam-London
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 nabu.de, including 18 speed issues, 6 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.