Website review, no card needed

schwartz-wba.com logo

schwartz-wba.com website review

Visit site (opens in a new tab)Reviewed 25 October 202638 issues · 72 checks

This review found 38 issues worth fixing on schwartz-wba.com, 13 of them high impact, across 72 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

Full-page screenshot of schwartz-wba.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix40
  • Use efficient cache lifetimes

    6.3 s · 14.3 MB

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

  • Reduce unused JavaScript

    7.7 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.7 s faster on a phone.

  • Improve image delivery

    5.3 s · 1.8 MB

    15 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.

  • Mobile performance score: 40

    40/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (YouTube, Google Tag Manager and Google Fonts and others), adding 2.3 MB and 814 ms of main-thread time.

  • YouTube adds 631 ms

    631 ms

    YouTube costs a phone 631 ms of main-thread work and 1.9 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.

  • Render-blocking requests

    450 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Google Tag Manager adds 183 ms

    183 ms

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

  • 9 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

6 to fix36
  • Largest Contentful Paint: 22.0 s

    22.0 s

    Your largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wenn Sie unter 16 Jahre alt sind und Ihre Zustimmung zu fre…”.

  • Time to Interactive: 23.0 s

    23.0 s

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

  • Speed Index: 10.1 s

    10.1 s

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

  • Cumulative Layout Shift: 0.456

    0.456

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Total Blocking Time: 209 ms

    209 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

4 to fix43
  • Page weight: 16.6 MB in 79 requests

    16.6 MB

    Your homepage downloads 16.6 MB in 79 requests on a phone: media 10.1 MB (3), images 4.1 MB (33) and scripts 2.0 MB (18). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.1 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.

  • 5 images below the first screen load straight away

    5 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images far larger than shown

    421 KiB

    4 images are downloaded at several times the size a phone draws them, for example 01_Weltweit-Weltkugel_CHINA.png at 1,000 px wide, shown at 256 px. Resized copies would save about 421 KiB.

  • About 4.7 g of CO₂ per visit

    4.70 g

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

Accessibility

4 to fixGoogle 9395
  • 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.

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

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

6 to fixGoogle 8573
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“Auf dem Weg zu mehr Nachhaltigkeit”, “Tailored Tempering” and “Leichter. Sicherer. Nachhaltiger.”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://schwartz-wba.com/sitemap.xml, so Google discovers your pages only by following links.

  • 2 links crawlers can't follow

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

  • 82 internal links, 6 external

    The homepage links to 82 pages on schwartz-wba.com and 6 external pages.

3 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Startseite: schwartz Wärmebehandlungsanlagen”.

  • Canonical URL set

    The canonical URL is https://schwartz-wba.com/de/.

  • robots.txt in place

    robots.txt is in place.

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://schwartz-wba.com/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 (477 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 15 pages without a meta description

    https://schwartz-wba.com/de/unternehmen, https://schwartz-wba.com/de/produkte, https://schwartz-wba.com/de/karriere, https://schwartz-wba.com/de/service, https://schwartz-wba.com/en and https://schwartz-wba.com/de/produkte/thermo-inline-printer and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://schwartz-wba.com/de/unternehmen has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://schwartz-wba.com/de/karriere took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 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 9287
  • 20 small tap targets

    20 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 694 words of visible text.

4 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 5 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 schwartz-wba.com, 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 Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on schwartz-wba.com, including 14 speed issues, 6 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