Website review, no card needed

hzdr.de logo

hzdr.de website review

Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 76 checks

This review found 41 issues worth fixing on hzdr.de, 19 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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.5 s1.1 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.3 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
121 ms79 msMay 30Nov 14116 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202684 ms
Jun 6, 202686 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202688 ms
Jul 4, 202689 ms
Jul 11, 202693 ms
Jul 18, 202696 ms
Jul 25, 202698 ms
Aug 1, 202697 ms
Aug 8, 202692 ms
Aug 15, 202691 ms
Aug 22, 202689 ms
Aug 29, 202689 ms
Sep 5, 202689 ms
Sep 12, 202686 ms
Sep 19, 202687 ms
Sep 26, 202688 ms
Oct 3, 202696 ms
Oct 10, 2026105 ms
Oct 17, 2026102 ms
Oct 24, 2026104 ms
Oct 31, 202698 ms
Nov 7, 202697 ms
Nov 14, 2026116 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 hzdr.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix39
  • Use efficient cache lifetimes

    1.2 s · 2.1 MB

    37 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

  • Render-blocking requests

    3.1 s

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

  • Reduce unused JavaScript

    2.4 s · 485 KiB

    About 485 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Mobile performance score: 39

    39/100

    Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    450 ms · 3.2 MB

    15 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 65 KiB

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

  • Font display

    150 ms

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

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

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

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

  • Server response: 116 ms

    116 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 9.9 s

    9.9 s

    Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Picture - Dresdens anderer Dynamo: HZDR eröffnet neue Großf…”.

  • Cumulative Layout Shift: 0.76

    0.76

    The layout shifts by 0.76 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 10.2 s

    10.2 s

    The page becomes fully interactive after 10.2 s. Good is under 3.8 s.

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

  • Real-user TTFB: 926 ms

    926 ms

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

  • 4 images without width and height

    4 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.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 89 ms

    89 ms

    Real visitors wait 89 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.6 s

    1.6 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix18
  • Page weight: 16.6 MB in 58 requests

    16.6 MB

    Your homepage downloads 16.6 MB in 58 requests on a phone: images 15.4 MB (36), scripts 983 KiB (12) and fonts 116 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 11.6 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    1.5 MB

    7 images are downloaded at several times the size a phone draws them, for example LinkBild_0272.jpg at 1,080 px wide, shown at 208 px. Resized copies would save about 1.5 MB.

  • 24 images in older formats

    24 images (14.4 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.

  • 15 images below the first screen load straight away

    15 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.7 g of CO₂ per visit

    4.69 g

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

Accessibility

4 to fixGoogle 9694
  • 3 text elements with low contrast

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

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

  • Meta description is long (506 characters)

    Your meta description is 506 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 111 internal links, 26 external

    The homepage links to 111 pages on hzdr.de and 26 external pages.

5 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “HZDR – Helmholtz-Zentrum Dresden-Rossendorf”.

  • Canonical URL set

    The canonical URL is https://www.hzdr.de/db/Cms?pOid=74004&pNid=0.

  • 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://www.hzdr.de/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 2 AI answer engine crawlers

    2 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot) and ChatGPT (ChatGPT-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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

  • Opted out of AI training for 2 crawlers

    robots.txt blocks GPTBot and ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (630 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix55
  • 1 page without a title

    https://www.hzdr.de/db/ContMan.Options.SetLangRedirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.hzdr.de/db/!ContMan.Search.Data is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.hzdr.de/db/Cms?pNid=0 and / all use the title “HZDR – Helmholtz-Zentrum Dresden-Rossendorf”. 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://www.hzdr.de/db/ContMan.Options.SetLangRedirect, https://www.hzdr.de/db/!Contman.Presse.Data, https://www.hzdr.de/db/!JobList and https://www.hzdr.de/db/!ContMan.Search.Data have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.hzdr.de/db/Cms?pOid=74004&pNid=0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    / and https://www.hzdr.de/db/ContMan.Options.SetLangRedirect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

1 checks passed
  • Linked pages load

    6 pages of 8 loaded without an error (the rest turned automated requests away).

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

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

2 checks passed
  • Tap targets are thumb-sized

    26 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 592 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact to Communications” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 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 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 hzdr.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
Astro
Hosting
Verein zur Foerderung eines Deutschen Forschungsnetzes e.V.

Company

Founded
1992
Headquarters
Dresden

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on hzdr.de, including 15 speed issues, 4 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

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