Website review, no card needed

stahlgear.de logo

stahlgear.de website review

Visit site (opens in a new tab)Reviewed 4 November 202639 issues · 87 checks

This review found 39 issues worth fixing on stahlgear.de, 16 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
2.1 s1.7 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
162 ms143 msMay 16Oct 31153 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026152 ms
May 23, 2026149 ms
May 30, 2026152 ms
Jun 6, 2026155 ms
Jun 13, 2026160 ms
Jun 20, 2026158 ms
Jun 27, 2026155 ms
Jul 4, 2026152 ms
Jul 11, 2026149 ms
Jul 18, 2026148 ms
Jul 25, 2026146 ms
Aug 1, 2026145 ms
Aug 8, 2026146 ms
Aug 15, 2026149 ms
Aug 22, 2026152 ms
Aug 29, 2026155 ms
Sep 5, 2026157 ms
Sep 12, 2026157 ms
Sep 19, 2026157 ms
Sep 26, 2026157 ms
Oct 3, 2026155 ms
Oct 10, 2026155 ms
Oct 17, 2026154 ms
Oct 24, 2026154 ms
Oct 31, 2026153 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 stahlgear.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stahlgear.de at 1.2 s1.2 s
  2. stahlgear.de at 2.4 s2.4 s
  3. stahlgear.de at 3.5 s3.5 s
  4. stahlgear.de at 4.7 s4.7 s
  5. stahlgear.de at 5.9 s5.9 s
  6. stahlgear.de at 7.1 s7.1 s
  7. stahlgear.de at 8.2 s8.2 s
  8. stahlgear.de at 9.4 s9.4 s

Speed

10 to fix44
  • Reduce unused JavaScript

    1.8 s · 636 KiB

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

  • Shopify adds 1.4 s

    1.4 s

    Shopify costs a phone 1.4 s of main-thread work and 1.4 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.

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 9.0 s

    A phone's processor spends 9.0 s on main-thread work while loading, 5.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,013 HTML elements

    The page has 3,013 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 2.7 MB and 2.8 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 555 ms. During a long task the page ignores taps.

  • Improve image delivery

    503 KiB

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

  • Google Tag Manager adds 438 ms

    438 ms

    Google Tag Manager costs a phone 438 ms of main-thread work and 343 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.

  • Klaviyo adds 362 ms

    362 ms

    Klaviyo costs a phone 362 ms of main-thread work and 599 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.

  • Use efficient cache lifetimes

    200 ms · 200 KiB

    15 files are served with short cache lifetimes, so returning visitors download them again (200 KiB).

  • Minify JavaScript

    220 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 62 KiB

    Polyfills for old browsers add 62 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    25 KiB

    About 25 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    6 KiB

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

  • 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: 32 ms

    32 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 15.0 s

    15.0 s

    Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “⭐⭐⭐⭐⭐ 4.8/5 · 15.000+ Bewertungen Gebaut für Hände, die wir…”.

  • Time to Interactive: 22.6 s

    22.6 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 5.5 s

    5.5 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • 5 images without width and height

    5 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

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

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

    +14%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s 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: 2.1 s

    2.1 s

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

  • Real-user INP: 121 ms

    121 ms

    Real 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.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 490 ms

    490 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 4.9 MB in 332 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 332 requests on a phone: scripts 2.0 MB (136), images 1.5 MB (29) and other files 959 KiB (137). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (930 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 1.4 g of CO₂ per visit

    1.38 g

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

2 checks passed
  • 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

7 to fixGoogle 8889
  • 21 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • 190 form fields without a label

    190 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 9284
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Gebaut für Hände, die wirklich arbeiten.” and “Gebaut für Hände, die wirklich arbeiten.”). One clear main headline is easier for people and search engines.

  • Meta description is long (308 characters)

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 146 internal links, 2 external

    The homepage links to 146 pages on stahlgear.de and 2 external pages.

5 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “StahlGear® Offizielle Website | Robuste Smartwatches & Zubehör”.

  • Canonical URL set

    The canonical URL is https://www.stahlgear.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.stahlgear.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.

3 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,517 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.stahlgear.de/llms.txt (10 KiB, 6 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.stahlgear.de/pages/quiz, https://www.stahlgear.de/pages/bogo-sale and https://www.stahlgear.de/products/multitool-karte have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.stahlgear.de/products/zeus-2-0-smartwatch, https://www.stahlgear.de/products/titan-pro-smartwatch, https://www.stahlgear.de/products/zeus-smartwatch, https://www.stahlgear.de/pages/quiz, https://www.stahlgear.de/products/zeus-one-smartwatch and https://www.stahlgear.de/products/nova-smartwatch and 3 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 53 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9289
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “SearchForm is not defined”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 682 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies, 1 of them by other companies (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.

  • 50 other companies contacted

    Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 stahlgear.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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
2 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on stahlgear.de, including 16 speed issues, 4 SEO issues and 4 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