Website review, no card needed
hansa-flex.de website review
Visit site (opens in a new tab)Reviewed 1 November 202640 issues · 87 checks
This review found 40 issues worth fixing on hansa-flex.de, 14 of them high impact, across 87 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 120 ms |
| May 16, 2026 | 121 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 126 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 129 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 130 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Use efficient cache lifetimes
6.2 s · 6.8 MB68 files are served with short cache lifetimes, so returning visitors download them again (6.8 MB).
Improve image delivery
3.0 s · 5.9 MB13 images could be 5.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
1.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 350 KiBAbout 350 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.
4 third-party services on the page
4 third-party services load with your homepage (consentmanager.net, Google CDN and jQuery CDN and others), adding 557 KiB and 654 ms of main-thread time.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
consentmanager.net adds 401 ms
401 msconsentmanager.net costs a phone 401 ms of main-thread work and 173 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 415 ms. During a long task the page ignores taps.
Reduce unused CSS
300 ms · 56 KiBAbout 56 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 801 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 220 ms
220 msGoogle CDN costs a phone 220 ms of main-thread work and 351 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.
2,081 HTML elements
The page has 2,081 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
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.
1 checks passed
Server response: 110 ms
110 msYour server sent the HTML in 110 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.3 s
8.3 sThe page becomes fully interactive after 8.3 s. Good is under 3.8 s.
Total Blocking Time: 621 ms
621 msScripts block taps and scrolling for 621 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
42 images without width and height
42 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 120 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 591 ms
591 msReal visitors wait 591 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.2 MB in 80 requests
7.2 MBYour homepage downloads 7.2 MB in 80 requests on a phone: images 6.3 MB (60), scripts 591 KiB (10) and fonts 273 KiB (5). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 5.6 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
2.6 MB6 images are downloaded at several times the size a phone draws them, for example csm_HANSA-FLEX-Fussballturnier-2026_11a4cbd341.webp at 1,232 px wide, shown at 290 px. Resized copies would save about 2.6 MB.
11 images in older formats
11 images (4.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.
About 2.1 g of CO₂ per visit
2.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.05 g of CO₂e: 246.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
ARIA commands must have an accessible name (2 elements)
ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (73 elements)
All page content should be contained by landmarks: 73 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 97 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Hydraulikbedarf online bestellen!” and “HANSA‑FLEX STEHT FÜR HYDRAULIK”). One clear main headline is easier for people and search engines.
353 internal links, 87 external
The homepage links to 353 pages on hansa-flex.de and 87 external pages.
7 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “HANSA-FLEX – Ihr Experte für Hydraulik und Fluidtechnik. Entdecken Sie maßgeschneiderte Lösungen für Ihre individuellen…”.
Title: 44 characters
Your title is a healthy 44 characters: “Ihr Systempartner für Hydraulik | HANSA-FLEX”.
Canonical URL set
The canonical URL is https://www.hansa-flex.de/.
Structured data in place
Structured data found: WebSite.
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.hansa-flex.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.hansa-flex.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,624 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://www.hansa-flex.de/niederlassungssuche and https://www.hansa-flex.de/spenden-statt-schenken have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.hansa-flex.de/niederlassungssuche has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.hansa-flex.de/unternehmen/aktuelles, https://www.hansa-flex.de/unternehmen/geschichte and https://www.hansa-flex.de/unternehmen/leitbild-und-werte took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 155 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
67 small tap targets
67 of 122 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 706 words of copy
The homepage carries about 706 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ZUM ONLINE-SHOP”.
4 calls to action
The homepage has 4 calls to action, for example “Online-Shop” and “Zum Online-Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 phone links and 2 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: consentmanager
A consent management tool (consentmanager) loads with the page.
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 hansa-flex.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
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Bremen Briteline GmbH
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on hansa-flex.de, including 21 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.