Website review, no card needed

amanngirrbach.com logo

amanngirrbach.com website review

Visit site (opens in a new tab)Reviewed 30 October 202636 issues · 80 checks

This review found 36 issues worth fixing on amanngirrbach.com, 14 of them high impact, across 80 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.6 s1.3 sMay 9Oct 241.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
84 ms74 msMay 9Oct 2477 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202683 ms
May 16, 202680 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202678 ms
Jun 20, 202676 ms
Jun 27, 202679 ms
Jul 4, 202678 ms
Jul 11, 202679 ms
Jul 18, 202677 ms
Jul 25, 202675 ms
Aug 1, 202676 ms
Aug 8, 202676 ms
Aug 15, 202678 ms
Aug 22, 202678 ms
Aug 29, 202678 ms
Sep 5, 202678 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202681 ms
Oct 3, 202680 ms
Oct 10, 202679 ms
Oct 17, 202678 ms
Oct 24, 202677 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 amanngirrbach.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amanngirrbach.com at 0.6 s0.6 s
  2. amanngirrbach.com at 1.3 s1.3 s
  3. amanngirrbach.com at 1.9 s1.9 s
  4. amanngirrbach.com at 2.5 s2.5 s
  5. amanngirrbach.com at 3.2 s3.2 s
  6. amanngirrbach.com at 3.8 s3.8 s
  7. amanngirrbach.com at 4.4 s4.4 s
  8. amanngirrbach.com at 5.1 s5.1 s

Speed

9 to fix41
  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 5.5 s

    A phone's processor spends 5.5 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,052 HTML elements

    The page has 3,052 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    1.9 MB

    13 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    440 ms · 260 KiB

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

  • Cookiebot adds 351 ms

    351 ms

    Cookiebot costs a phone 351 ms of main-thread work and 153 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.

  • 20 long tasks on the main thread

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

  • Google Fonts adds 9 ms

    9 ms

    Google Fonts costs a phone 9 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Cookiebot, jQuery CDN and Google Fonts and others), adding 791 KiB and 413 ms of main-thread time.

  • Use efficient cache lifetimes

    250 ms · 37 KiB

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

  • Reduce unused CSS

    150 ms · 57 KiB

    About 57 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.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

9 to fix100
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Speed Index: 16.0 s

    16.0 s

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

  • Time to Interactive: 30.4 s

    30.4 s

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

  • Cumulative Layout Shift: 0.609

    0.609

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user TTFB: 816 ms

    816 ms

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

  • Total Blocking Time: 467 ms

    467 ms

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”. Most of its time is element render delay (2.3 s).

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

4 checks passed
  • 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: 78 ms

    78 ms

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

Images and page weight

4 to fix43
  • Page weight: 16.5 MB in 191 requests

    16.5 MB

    Your homepage downloads 16.5 MB in 191 requests on a phone: images 8.7 MB (109), media 6.6 MB (1) and scripts 852 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (914 KiB) 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.

  • 3 images below the first screen load straight away

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

  • 2 images far larger than shown

    141 KiB

    2 images are downloaded at several times the size a phone draws them, for example ceramill-motion-air-rfid-1200x1200-3.png at 1,200 px wide, shown at 350 px. Resized copies would save about 141 KiB.

  • About 4.7 g of CO₂ per visit

    4.68 g

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

Accessibility

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

  • 4 images without alt text

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

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

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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

1 to fixGoogle 9298
  • 10 links with vague text

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

  • 303 internal links, 14 external

    The homepage links to 303 pages on amanngirrbach.com and 14 external pages.

8 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Complete CAD/CAM solutions from Amann Girrbach for dental practices and labs: milling machines, scanners, software and …”.

  • One H1 headline

    Your main headline reads: “CAD/CAM Solutions for Dentists and Dental Laboratories”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Amann Girrbach - Work for a Smile”.

  • Canonical URL set

    The canonical URL is https://www.amanngirrbach.com/en-gb/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • Open Graph tags complete

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

  • 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.amanngirrbach.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.amanngirrbach.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 (2,533 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.amanngirrbach.com/en-gb and / all use the title “Amann Girrbach - Work for a Smile”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://www.amanngirrbach.com/en-gb. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.amanngirrbach.com/en-gb/contact has 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 84 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://www.amanngirrbach.com/en-gb/wp-content/uploads/sites/2/2026/03/Barbara-Wetzel-400x600.jpg.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    16 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 1,360 words of copy

    The homepage carries about 1,360 words of visible text.

3 checks passed
  • 29 calls to action

    The homepage has 29 calls to action, for example “Learn more”, “Start now” and “Contact”.

  • 1 short form

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

  • Direct contact links

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

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 amanngirrbach.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
WordPress
Framework
jQuery
Hosting
WP Engine

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on amanngirrbach.com, including 18 speed issues, 1 SEO issue 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