Website review, no card needed

hellweg.de logo

hellweg.de website review

Visit site (opens in a new tab)Reviewed 30 October 202635 issues · 91 checks

This review found 35 issues worth fixing on hellweg.de, 13 of them high impact, across 91 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.8 s734 msMay 9Oct 24879 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 2026959 ms
Oct 3, 2026857 ms
Oct 10, 2026882 ms
Oct 17, 2026884 ms
Oct 24, 2026879 ms
Real-visitor tap response (INP)75th percentile, phones
134 ms92 msMay 9Oct 24104 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026123 ms
May 16, 2026122 ms
May 23, 2026121 ms
May 30, 2026121 ms
Jun 6, 2026122 ms
Jun 13, 2026124 ms
Jun 20, 2026123 ms
Jun 27, 2026126 ms
Jul 4, 2026127 ms
Jul 11, 2026127 ms
Jul 18, 2026128 ms
Jul 25, 2026128 ms
Aug 1, 2026129 ms
Aug 8, 2026129 ms
Aug 15, 2026129 ms
Aug 22, 2026128 ms
Aug 29, 2026127 ms
Sep 5, 2026121 ms
Sep 12, 2026113 ms
Sep 19, 2026107 ms
Sep 26, 2026103 ms
Oct 3, 202697 ms
Oct 10, 2026100 ms
Oct 17, 2026103 ms
Oct 24, 2026104 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 hellweg.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hellweg.de at 0.4 s0.4 s
  2. hellweg.de at 0.8 s0.8 s
  3. hellweg.de at 1.2 s1.2 s
  4. hellweg.de at 1.6 s1.6 s
  5. hellweg.de at 2.0 s2.0 s
  6. hellweg.de at 2.4 s2.4 s
  7. hellweg.de at 2.8 s2.8 s
  8. hellweg.de at 3.2 s3.2 s

hellweg.de does not allow embedding, so this is Google's rendering of the page.

Speed

11 to fix48
  • Use efficient cache lifetimes

    8.6 s · 2.2 MB

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

  • Reduce unused JavaScript

    4.8 s · 995 KiB

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

  • Render-blocking requests

    2.1 s

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

  • Mobile performance score: 48

    48/100

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (hellweg.digital, Usercentrics CMP and ecn-ldr.de), adding 2.4 MB and 597 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 149 KiB

    About 149 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • hellweg.digital adds 436 ms

    436 ms

    hellweg.digital costs a phone 436 ms of main-thread work and 2.1 MB 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.

  • Legacy JavaScript

    300 ms · 103 KiB

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

  • 6 long tasks on the main thread

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

  • Improve image delivery

    304 KiB

    1 image could be 304 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Usercentrics CMP adds 131 ms

    131 ms

    Usercentrics CMP costs a phone 131 ms of main-thread work and 309 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.

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

2 checks passed
  • Main-thread work: 1.6 s

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

  • Server response: 70 ms

    70 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 11.4 s

    11.4 s

    Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.193

    0.193

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

  • Total Blocking Time: 317 ms

    317 ms

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

  • 1 image without width and height

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

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

    1.1 s

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

  • Real-user INP: 100 ms

    100 ms

    Real visitors wait 100 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.8 s

    0.8 s

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

  • Real-user TTFB: 363 ms

    363 ms

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

  • Largest content (LCP) got 47% faster for real visitors

    -47%

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

Images and page weight

2 to fix81
  • Page weight: 2.4 MB in 66 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 66 requests on a phone: scripts 1.7 MB (40), images 375 KiB (6) and stylesheets 137 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Mobile_703x500px_wk8-01.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).

  • 1 image in older formats

    1 image (360 KiB) is 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.7 g of CO₂ per visit

    0.69 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9696
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 9296
  • No robots.txt

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

  • 5 internal links, 1 external

    The homepage links to 5 pages on hellweg.de and 1 external page.

7 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Ihr Baumarkt fürs Heimwerken, Bauen und Garten >> Top Beratung & Serviceleistungen durch Profis ✓ Große Auswahl an Prod…”.

  • One H1 headline

    Your main headline reads: “HELLWEG Die Profi-Bau- & Gartenmärkte”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “HELLWEG Baumarkt & Online-Shop - Heimwerken und Garten”.

  • Canonical URL set

    The canonical URL is https://www.hellweg.de/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.hellweg.de/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no /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.

1 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

5 to fix55
  • 2 pages without a title

    /widgets/cms/c3a905f8465f451f97e399d48a59871f and /widgets/cms/3866747713664b2587b6f591d97f0d40 have no <title>, so Google invents the link text in results.

  • 1 page points its canonical at the homepage

    /widgets/cms/846e5ab59c0849cfa5fa52cf6af3e315 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 linked pages hidden from search

    /widgets/cms/c3a905f8465f451f97e399d48a59871f and /widgets/cms/3866747713664b2587b6f591d97f0d40 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    / and /widgets/cms/846e5ab59c0849cfa5fa52cf6af3e315 all use the title “HELLWEG Baumarkt & Online-Shop - Heimwerken und Garten”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    /widgets/cms/c3a905f8465f451f97e399d48a59871f and /widgets/cms/3866747713664b2587b6f591d97f0d40 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    /widgets/cms/846e5ab59c0849cfa5fa52cf6af3e315 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.

  • 4 internal pages checked

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

2 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

Best practices

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://integrations.etrusted.com/applications/widget.js/v2' violates the following Content Securit…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

8 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (hellweg.de).

  • Valid certificate (173 days left)

    The certificate from DigiCert Inc · Thawte TLS RSA CA G1 verifies for hellweg.de and is valid for another 173 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://hellweg.de redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 6 links work

    All 6 links checked from your homepage (5 internal, 1 external) answered without errors.

Domain and trust

1 checks passed
  • Certificate issuers are restricted

    CAA records allow only www.digicert.com and letsencrypt.org to issue certificates for hellweg.de, so a mis-issued certificate from anyone else is refused.

Content and conversion

5 to fix43
  • 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.

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

  • Only about 55 words

    The homepage has only about 55 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Email authentication

100
  • Email authentication score: 100/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 ip4:145.253.78.114 a:smtp.twt.net a:smtp.twt.services ip4:49.13.130.189 include:_spf.atlassian.net include:spf.p…”.

  • DKIM signing found

    A DKIM key is published (selector “s1” and “s2”), so receivers can verify mail really came from you.

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (measured from a US location before any click).

  • 9 other companies contacted

    Loading the homepage contacts 9 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).

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Analytics
Google Tag Manager
Hosting
Netcologne

Company

Employees
4,000
Founded
1971
Headquarters
Dortmund

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on hellweg.de, including 18 speed issues, 1 SEO issue and 5 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