Website review, no card needed

salzwerke.de logo

salzwerke.de website review

Visit site (opens in a new tab)Reviewed 22 October 202633 issues · 84 checks

This review found 33 issues worth fixing on salzwerke.de, 11 of them high impact, across 84 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
1.0 s832 msMay 2Oct 17995 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026904 ms
May 9, 2026863 ms
May 16, 2026853 ms
May 23, 2026859 ms
May 30, 2026857 ms
Jun 6, 2026866 ms
Jun 13, 2026885 ms
Jun 20, 2026890 ms
Jun 27, 2026909 ms
Jul 4, 2026910 ms
Jul 11, 2026913 ms
Jul 18, 2026921 ms
Jul 25, 2026937 ms
Aug 1, 2026951 ms
Aug 8, 2026954 ms
Aug 15, 2026938 ms
Aug 22, 2026926 ms
Aug 29, 2026934 ms
Sep 5, 2026927 ms
Sep 12, 2026939 ms
Sep 19, 2026946 ms
Sep 26, 2026953 ms
Oct 3, 2026968 ms
Oct 10, 2026970 ms
Oct 17, 2026995 ms
Real-visitor tap response (INP)75th percentile, phones
72 ms69 msMay 2Oct 1771 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202670 ms
May 9, 202670 ms
May 16, 202669 ms
May 23, 202670 ms
May 30, 202670 ms
Jun 6, 202670 ms
Jun 13, 202671 ms
Jun 20, 202671 ms
Jun 27, 202672 ms
Jul 4, 202672 ms
Jul 11, 202671 ms
Jul 18, 202671 ms
Jul 25, 202671 ms
Aug 1, 202670 ms
Aug 8, 202670 ms
Aug 15, 202670 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202670 ms
Sep 26, 202670 ms
Oct 3, 202670 ms
Oct 10, 202671 ms
Oct 17, 202671 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 salzwerke.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix73
  • Render-blocking requests

    1.9 s

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

  • Improve image delivery

    1.1 s · 708 KiB

    16 images could be 708 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    460 ms · 50 KiB

    About 50 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • Reduce unused CSS

    460 ms · 47 KiB

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

  • Font display

    500 ms

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cookiebot), adding 159 KiB and 154 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    34 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 73. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Das Salz wird in den Bergwerken Heilbronn und Berchtesgaden…”.

  • Time to Interactive: 7.4 s

    7.4 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • 2 images without width and height

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

  • 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 70 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +11%

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

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.3 s

    1.3 s

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

  • Real-user INP: 72 ms

    72 ms

    Real visitors wait 72 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.2 s

    1.2 s

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

  • Real-user TTFB: 589 ms

    589 ms

    Real visitors wait 589 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).

  • Total Blocking Time: 32 ms

    32 ms

    Scripts block the page for only 32 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix65
  • Page weight: 2.0 MB in 72 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 72 requests on a phone: images 1.5 MB (21), scripts 411 KiB (36) and stylesheets 68 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.3 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.

  • 1 image far larger than shown

    154 KiB

    1 image is downloaded at several times the size a phone draws it, for example Salzberg_Probe.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 154 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (133 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.57 g

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

Accessibility

9 to fixGoogle 8489
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 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.

  • 17 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 10084
  • No structured data

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

  • Meta description is long (223 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 131 internal links, 9 external

    The homepage links to 131 pages on salzwerke.de and 9 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Glückauf!”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “Startseite: SÜDWESTDEUTSCHE SALZWERKE AG”.

  • Canonical URL set

    The canonical URL is https://www.salzwerke.de/de/startseite.html.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.salzwerke.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.salzwerke.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 (313 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix74
  • 1 linked page is broken

    Your homepage links to https://www.salzwerke.de/de/.main-navi, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 14 pages share a meta description

    https://www.salzwerke.de/de/kontakt.html, https://www.salzwerke.de/de/downloads.html, https://www.salzwerke.de/en/home.html, https://www.salzwerke.de/de/unternehmen.html, https://www.salzwerke.de/de/unternehmen/im-ueberblick.html and https://www.salzwerke.de/de/unternehmen/vorstand.html and 8 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 93 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 10093
  • 16 small tap targets

    16 of 35 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

2 to fix60
  • 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.

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

    The homepage carries about 307 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Start-up Engagement”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Matomo.

Privacy and tracking

  • 2 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 salzwerke.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
Matomo

Company

Employees
1,016
Founded
1883
Headquarters
Heilbronn

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on salzwerke.de, including 11 speed issues, 4 SEO issues and 2 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