Website review, no card needed

bihler.de logo

bihler.de website review

Visit site (opens in a new tab)Reviewed 30 October 202632 issues · 70 checks

This review found 32 issues worth fixing on bihler.de, 11 of them high impact, across 70 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.2 s943 msMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 2026977 ms
May 16, 20261.0 s
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
89 ms78 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202679 ms
May 16, 202681 ms
May 23, 202682 ms
May 30, 202683 ms
Jun 6, 202683 ms
Jun 13, 202681 ms
Jun 20, 202682 ms
Jun 27, 202686 ms
Jul 4, 202684 ms
Jul 11, 202680 ms
Jul 18, 202680 ms
Jul 25, 202681 ms
Aug 1, 202687 ms
Aug 8, 202686 ms
Aug 15, 202688 ms
Aug 22, 202687 ms
Aug 29, 202684 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202685 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202687 ms
Oct 17, 202688 ms
Oct 24, 202687 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 bihler.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bihler.de at 0.5 s0.5 s
  2. bihler.de at 1.1 s1.1 s
  3. bihler.de at 1.6 s1.6 s
  4. bihler.de at 2.1 s2.1 s
  5. bihler.de at 2.7 s2.7 s
  6. bihler.de at 3.2 s3.2 s
  7. bihler.de at 3.7 s3.7 s
  8. bihler.de at 4.3 s4.3 s

Speed

4 to fix64
  • Use efficient cache lifetimes

    1.3 s · 2.6 MB

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

  • Render-blocking requests

    1.7 s

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    750 ms · 116 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (gal-digital.de, Google Tag Manager and Google/Doubleclick Ads), adding 218 KiB and 302 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 26 KiB

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

  • 1 long task on the main thread

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

  • Improve image delivery

    30 KiB

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

  • 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: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 373 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

6 to fix100
  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BIHLER DIGITAL Connecting Possibilities Learn more”.

  • Speed Index: 7.0 s

    7.0 s

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

  • Time to Interactive: 8.0 s

    8.0 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 18 images without width and height

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

  • Cumulative Layout Shift: 0.106

    0.106

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

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 ms to 87 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-24, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.2 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: 1.2 s

    1.2 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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.0 s

    1.0 s

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

  • Real-user TTFB: 544 ms

    544 ms

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

  • Total Blocking Time: 28 ms

    28 ms

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

Images and page weight

5 to fix31
  • 1 image over 500 KB

    leantool-fvb-bihler.gif weighs 1.0 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    748 KiB

    4 images are downloaded at several times the size a phone draws them, for example leantool-fvb-bihler.gif at 1,536 px wide, shown at 390 px. Resized copies would save about 748 KiB.

  • Page weight: 2.9 MB in 51 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 51 requests on a phone: images 2.5 MB (25), scripts 302 KiB (14) and stylesheets 47 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (1.5 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.

  • An image on the first screen is lazy-loaded

    whitepaper-elektro-mobilitaet-bihler-en.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).

  • About 0.8 g of CO₂ per visit

    0.81 g

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

Accessibility

3 to fixGoogle 10095
  • 7 images without alt text

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

  • 14 links without text

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

  • 8 form fields without a label

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

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

7 to fixGoogle 9271
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (164 characters)

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

  • Structured data has 1 problem

    Structured data found (RegularPage) but with 1 problem, for example “RegularPage: @context is not schema.org (https://schema.contao.org/)”.

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

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 107 internal links, 9 external

    The homepage links to 107 pages on bihler.de and 9 external pages.

3 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “Otto Bihler Maschinenfabrik GmbH & Co. KG - Bihler”.

  • 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.bihler.de/sitemap-xml.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.bihler.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

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

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://www.bihler.de/en/en, https://www.bihler.de/en/en/automation-technology-mechanical-engineering.html, https://www.bihler.de/en/en/automation-technology-mechanical-engineering/machines.html, https://www.bihler.de/en/en/automation-technology-mechanical-engineering/servo-modules.html, https://www.bihler.de/en/en/automation-technology-mechanical-engineering/toolmaking-tool-solution/stamping-forming-machine-lean-tool.html and https://www.bihler.de/en/en/automation-technology-mechanical-engineering/toolmaking-tool-solution/tool-coating.html and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

1 to fixGoogle 9293
  • 4 small tap targets

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

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

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

3 to fix67
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 9-field form

    Your longest form asks for 9 fields (5 required). Every extra field lowers completion.

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

    The homepage carries about 349 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more” and “Order free”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact Soldering”, “Contact” and “Download Center”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 bihler.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
Contao Open Source CMS
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Telemaxx

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on bihler.de, including 10 speed issues, 7 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