Website review, no card needed

schachermayer.at logo

schachermayer.at website review

Visit site (opens in a new tab)Reviewed 28 October 202629 issues · 73 checks

This review found 29 issues worth fixing on schachermayer.at, 9 of them high impact, across 73 checks. The most urgent: improve image delivery. 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.6 s1.2 sMay 9Oct 241.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
98 ms85 msMay 9Oct 2494 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202691 ms
May 16, 202691 ms
May 23, 202692 ms
May 30, 202690 ms
Jun 6, 202690 ms
Jun 13, 202689 ms
Jun 20, 202687 ms
Jun 27, 202686 ms
Jul 4, 202688 ms
Jul 11, 202687 ms
Jul 18, 202690 ms
Jul 25, 202691 ms
Aug 1, 202691 ms
Aug 8, 202694 ms
Aug 15, 202693 ms
Aug 22, 202695 ms
Aug 29, 202695 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202694 ms
Sep 26, 202694 ms
Oct 3, 202694 ms
Oct 10, 202694 ms
Oct 17, 202694 ms
Oct 24, 202694 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 schachermayer.at (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix69
  • Improve image delivery

    1.2 s · 1.4 MB

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

  • Render-blocking requests

    2.1 s

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 2.1 s.

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    450 ms · 84 KiB

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

  • Reduce unused CSS

    300 ms · 55 KiB

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

  • Minify JavaScript

    150 ms · 30 KiB

    30 KiB could be saved by minifying JavaScript.

  • Font display

    100 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 69 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    21 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (21 KiB).

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (schachermayer.com), adding 53 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 34.4 s

    34.4 s

    Your largest element takes 34.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Verkaufsräume in Collagen”.

  • Time to Interactive: 34.8 s

    34.8 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • 1 image without width and height

    1 image 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-24, real Chrome visitors' tap response (inp) went from 91 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 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.0 s

    2.0 s

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

  • Real-user INP: 81 ms

    81 ms

    Real visitors wait 81 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.9 s

    0.9 s

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

  • Real-user TTFB: 465 ms

    465 ms

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

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

    -13%

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

  • Cumulative Layout Shift: 0.004

    0.004

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

5 to fix18
  • Page weight: 7.2 MB in 44 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 44 requests on a phone: images 6.6 MB (26), scripts 235 KiB (9) and fonts 206 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    542 KiB

    1 image is downloaded at several times the size a phone draws it, for example hue1_19_APP.jpg at 1,500 px wide, shown at 369 px. Resized copies would save about 542 KiB.

  • 10 images in older formats

    10 images (2.9 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 below the first screen load straight away

    1 image further down the page (1.2 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    2.03 g

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

Accessibility

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 46 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: 46 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

3 to fixGoogle 10085
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Großhändler für technische Produkte und Designlösungen | SCHACHERMAYER ® [AT]”.

  • Meta description is long (237 characters)

    Your meta description is 237 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.

  • 65 internal links, 38 external

    The homepage links to 65 pages on schachermayer.at and 38 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “100.000 Artikel aus einer Hand”.

  • Canonical URL set

    The canonical URL is https://www.schachermayer.at/.

  • Structured data in place

    Structured data found: BreadcrumbList and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.schachermayer.at/suche and https://www.schachermayer.at/unternehmen/aktuelles are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://www.schachermayer.at/suche, https://www.schachermayer.at/unternehmen/dienstleistungen/sch-plus, https://www.schachermayer.at/unternehmen/seit-1838/meilensteine and https://www.schachermayer.at/unternehmen/kontakt/mediacenter have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.schachermayer.at/karriere and https://www.schachermayer.at/unternehmen/dienstleistungen/sch-plus 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 39 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 25 small tap targets

    25 of 44 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: the server responded with a status of 500 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 473 words of visible text.

3 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Matomo.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • 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 schachermayer.at, 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
Analytics
Matomo
Hosting
TTM

Company

Founded
1838
Headquarters
Linz

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on schachermayer.at, including 10 speed issues, 3 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

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