Website review, no card needed

buehler.com logo

buehler.com website review

Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 95 checks

This review found 41 issues worth fixing on buehler.com, 15 of them high impact, across 95 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
4.0 s2.2 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.8 s
May 23, 20263.6 s
May 30, 20263.6 s
Jun 6, 20263.5 s
Jun 13, 20263.5 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.7 s
Jul 25, 20263.6 s
Aug 1, 20263.5 s
Aug 8, 20263.3 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
210 ms156 msMay 16Oct 31204 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026167 ms
May 23, 2026167 ms
May 30, 2026164 ms
Jun 6, 2026163 ms
Jun 13, 2026165 ms
Jun 20, 2026167 ms
Jun 27, 2026171 ms
Jul 4, 2026172 ms
Jul 11, 2026170 ms
Jul 18, 2026170 ms
Jul 25, 2026165 ms
Aug 1, 2026162 ms
Aug 8, 2026166 ms
Aug 15, 2026172 ms
Aug 22, 2026179 ms
Aug 29, 2026184 ms
Sep 5, 2026184 ms
Sep 12, 2026185 ms
Sep 19, 2026191 ms
Sep 26, 2026192 ms
Oct 3, 2026196 ms
Oct 10, 2026204 ms
Oct 17, 2026197 ms
Oct 24, 2026204 ms
Oct 31, 2026204 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 buehler.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. buehler.com at 0.5 s0.5 s
  2. buehler.com at 1.1 s1.1 s
  3. buehler.com at 1.6 s1.6 s
  4. buehler.com at 2.1 s2.1 s
  5. buehler.com at 2.6 s2.6 s
  6. buehler.com at 3.1 s3.1 s
  7. buehler.com at 3.7 s3.7 s
  8. buehler.com at 4.2 s4.2 s

Speed

11 to fix39
  • Render-blocking requests

    3.9 s

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

  • Reduce unused JavaScript

    1.4 s · 539 KiB

    About 539 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.2 s · 338 KiB

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

  • Mobile performance score: 39

    39/100

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

  • Main-thread work: 4.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Accessibe Accessibility Overlay and others), adding 1.4 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    750 ms · 251 KiB

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

  • Google Tag Manager adds 530 ms

    530 ms

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

  • Facebook adds 276 ms

    276 ms

    Facebook costs a phone 276 ms of main-thread work and 213 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.

  • 15 long tasks on the main thread

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

  • 2,627 HTML elements

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

  • Minify CSS

    170 ms · 3 KiB

    3 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    150 ms · 17 KiB

    Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    150 ms

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

  • Improve image delivery

    132 KiB

    6 images could be 132 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 5 ms

    5 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 14.9 s

    14.9 s

    Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Solutions for Materials Preparation, Testing & Analysis Met…”.

  • Time to Interactive: 20.3 s

    20.3 s

    The page becomes fully interactive after 20.3 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.

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Total Blocking Time: 733 ms

    733 ms

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

  • Real-user INP: 243 ms

    243 ms

    Real visitors wait 243 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 22% slower for real visitors

    +22%

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

  • 1 image without width and height

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 498 ms

    498 ms

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

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

    -33%

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

  • Cumulative Layout Shift: 0.014

    0.014

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

Images and page weight

1 to fix85
  • Page weight: 3.8 MB in 175 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 175 requests on a phone: scripts 1.6 MB (40), images 1.4 MB (48) and fonts 345 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (172 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.

  • 1 image below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.07 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 8489
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

  • 212 form fields without a label

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

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

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 57 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No XML sitemap

    No XML sitemap at https://www.buehler.com/fr/sitemap_index.xml, so Google discovers your pages only by following links.

  • 3 links with vague text

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

  • 172 internal links, 9 external

    The homepage links to 172 pages on buehler.com and 9 external pages.

7 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Buehler provides metallography equipment, consumables, hardness testers and solutions for metallographic sample prepara…”.

  • One H1 headline

    Your main headline reads: “Metallographic Equipment for Sample Preparation”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Metallography Equipment for Sample Preparation | Buehler”.

  • Canonical URL set

    The canonical URL is https://www.buehler.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    44%

    The HTML your server sends has 1,285 of the 2,895 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

    The site publishes https://www.buehler.com/llms.txt (6 KiB, 12 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6983
  • 22 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Sending form data to 'https://www.facebook.com/tr/' violates the following report-only Content Security Policy directiv…”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 2,895 words of copy

    The homepage carries about 2,895 words of visible text.

6 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Learn More”, “Service Request” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Umami.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 1 of them by other companies (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.

  • 25 other companies contacted

    Loading the homepage contacts 25 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 buehler.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
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Employees
15,510

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on buehler.com, including 20 speed issues, 2 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