Website review, no card needed
hama-karriere.de website review
Visit site (opens in a new tab)Reviewed 4 November 202626 issues · 79 checks
This review found 26 issues worth fixing on hama-karriere.de, 9 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 104 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 108 ms |
| Jul 25, 2026 | 106 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 108 ms |
| Sep 12, 2026 | 103 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 102 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 105 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.4 s
0.8 s
1.3 s
1.7 s
2.1 s
2.5 s
3.0 s
3.4 s
Speed
Render-blocking requests
1.1 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 78
78/100Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
848 KiBAbout 848 KiB of JavaScript is downloaded but never used on this page.
4 third-party services on the page
4 third-party services load with your homepage (YouTube, Usercentrics CMP and Other Google APIs/SDKs and others), adding 1.3 MB and 694 ms of main-thread time.
Improve image delivery
250 ms · 381 KiB7 images could be 381 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
YouTube adds 461 ms
461 msYouTube costs a phone 461 ms of main-thread work and 977 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 CSS
310 ms · 168 KiBAbout 168 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 35 KiB3 files are served with short cache lifetimes, so returning visitors download them again (35 KiB).
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
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: 111 ms
111 msYour server sent the HTML in 111 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 15.8 s
15.8 sThe page becomes fully interactive after 15.8 s. Good is under 3.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Frau in roter Kleidung auf hellblauem Hintergrund vor histo…”.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 104 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 105 ms
105 msReal visitors wait 105 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 480 ms
480 msReal visitors wait 480 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 163 ms
163 msScripts block the page for only 163 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.081
0.081The layout barely moves while loading (CLS 0.081, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 57 requests
2.8 MBYour homepage downloads 2.8 MB in 57 requests on a phone: scripts 1.4 MB (21), fonts 614 KiB (6) and images 582 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.6 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
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 8 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Karriere bei Hama: Jobs und Perspektiven entdecken | Hama Karriere”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
52 internal links, 0 external
The homepage links to 52 pages on hama-karriere.de and 0 external pages.
6 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “Entdecke Jobs und Karrierechancen bei Hama. Werde Teil eines innovativen Teams. ✓ Karriere bei Hama. An Neuem wachsen.”.
One H1 headline
Your main headline reads: “Wir ziehen unsere Stärke aus dem Neuen. Du auch?”.
Canonical URL set
The canonical URL is https://www.hama-karriere.de/.
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.hama-karriere.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.hama-karriere.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 (339 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.hama-karriere.de/arbeiten-bei-hama/arbeitswelten/personalabteilung, which answers with an error. Visitors hit a dead end and search engines drop it.
1 linked page hidden from search
https://www.hama-karriere.de/arbeiten-bei-hama/arbeitswelten/facility-management is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a meta description
https://www.hama-karriere.de/arbeiten-bei-hama, https://www.hama-karriere.de/ausbildung-duales-studium and https://www.hama-karriere.de/arbeiten-bei-hama/arbeiten-in-monheim-bayern use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://www.hama-karriere.de/rund-ums-bewerben has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
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 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 284 words of copy
The homepage carries about 284 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Hama Shop”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 hama-karriere.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Oskar-von-Miller-Str. 1b
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
- Careers page
- www.hama-karriere.de/jobs (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on hama-karriere.de, including 13 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.