Website review, no card needed

maximator-hydrogen.de logo

maximator-hydrogen.de website review

Visit site (opens in a new tab)Reviewed 21 October 202622 issues · 74 checks

This review found 22 issues worth fixing on maximator-hydrogen.de, 4 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
936 ms565 msMay 2Oct 17762 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026750 ms
May 9, 2026750 ms
May 16, 2026776 ms
May 23, 2026871 ms
May 30, 2026795 ms
Jun 6, 2026819 ms
Jun 13, 2026812 ms
Jun 20, 2026716 ms
Jun 27, 2026767 ms
Jul 4, 2026736 ms
Jul 18, 2026621 ms
Jul 25, 2026608 ms
Aug 1, 2026644 ms
Aug 8, 2026620 ms
Aug 15, 2026665 ms
Aug 22, 2026667 ms
Aug 29, 2026688 ms
Oct 3, 2026820 ms
Oct 10, 2026893 ms
Oct 17, 2026762 ms
Real-visitor tap response (INP)75th percentile, phones
99 ms84 msMay 2Oct 1789 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202688 ms
May 9, 202688 ms
May 16, 202689 ms
May 23, 202697 ms
May 30, 202691 ms
Jun 6, 202689 ms
Jun 13, 202691 ms
Jun 20, 202686 ms
Jun 27, 202695 ms
Jul 4, 202693 ms
Jul 18, 202687 ms
Jul 25, 202686 ms
Aug 1, 202687 ms
Aug 22, 202694 ms
Aug 29, 202690 ms
Oct 3, 202694 ms
Oct 10, 202689 ms
Oct 17, 202689 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 maximator-hydrogen.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix86
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 86

    86/100

    Your mobile performance score is 86 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Font display

    400 ms

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (jQuery CDN), adding 24 KiB and 16 ms of main-thread time.

  • Improve image delivery

    16 KiB

    2 images could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    16 KiB

    Polyfills for old browsers add 16 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    6 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.3 s

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

  • Server response: 91 ms

    91 ms

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

Core Web Vitals

3 to fix100
  • Speed Index: 4.7 s

    4.7 s

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

  • Cumulative Layout Shift: 0.164

    0.164

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diese Website benutzt Cookies, die für den technischen Betr…”. Most of its time is element render delay (2.9 s).

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 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: 0.8 s

    0.8 s

    Real visitors wait 0.8 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: 0.6 s

    0.6 s

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

  • Real-user TTFB: 422 ms

    422 ms

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Time to Interactive: 2.6 s

    2.6 s

    The page is fully interactive after 2.6 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

1 to fix97
  • An image on the first screen is lazy-loaded

    Headergrafik-Desktop.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images in older formats

    2 images (83 KiB) 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.

  • About 0.3 g of CO₂ per visit

    0.26 g

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

2 checks passed
  • Page weight: 933 KiB in 47 requests

    933 KiB

    Your homepage downloads 933 KiB in 47 requests on a phone: images 796 KiB (31), scripts 61 KiB (6) and fonts 42 KiB (3). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8894
  • Positive tabindex

    6 elements have a tabindex above 0, which scrambles the keyboard order.

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

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 10 links without text

    10 visible links have no text or label, so screen readers cannot say where they go.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

5 to fixGoogle 10079
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Messen & Events 2025”, “Green Hydrogen Hub Stuttgart mit Pipeline-Einspei…” and “MAX Dispenser 1.5 - die neue Generation!”). One clear main headline is easier for people and search engines.

  • Meta description is long (251 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at maximator-hydrogen.de/robots.txt, the first file search crawlers ask for.

  • 35 internal links, 9 external

    The homepage links to 35 pages on maximator-hydrogen.de and 9 external pages.

3 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Maximator Hydrogen - Startseite von Maximator Hydrogen”.

  • Canonical URL set

    The canonical URL is https://www.maximator-hydrogen.de/home.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.maximator-hydrogen.de/sitemap.xml.

AI search readiness

1 to fix88
  • 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.maximator-hydrogen.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 (629 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 4 pages share a title

    https://www.maximator-hydrogen.de/newsroom, https://www.maximator-hydrogen.de/newsroom/messen-events-2025, https://www.maximator-hydrogen.de/newsroom/stadtwerke-stuttgart-beauftragen-maximator-hydrogen-fuer-green-hydrogen-hub-stuttgart and https://www.maximator-hydrogen.de/newsroom/max-dispenser-15 all use the title “Maximator Hydrogen - Hydrogen Newsroom”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://www.maximator-hydrogen.de/newsroom, https://www.maximator-hydrogen.de/newsroom/messen-events-2025, https://www.maximator-hydrogen.de/newsroom/stadtwerke-stuttgart-beauftragen-maximator-hydrogen-fuer-green-hydrogen-hub-stuttgart and https://www.maximator-hydrogen.de/newsroom/max-dispenser-15 use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://www.maximator-hydrogen.de/produktportfolio, https://www.maximator-hydrogen.de/services, https://www.maximator-hydrogen.de/newsroom, https://www.maximator-hydrogen.de/unternehmen, https://www.maximator-hydrogen.de/karriere and https://www.maximator-hydrogen.de/download and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 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.

  • 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 to fixGoogle 10093
  • 9 small tap targets

    9 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 687 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Download”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Download”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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 maximator-hydrogen.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
Framework
Vue.js
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on maximator-hydrogen.de, including 6 speed issues, 5 SEO issues and 1 conversion gap. 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