Website review, no card needed

bauerfeind.us logo

bauerfeind.us website review

Visit site (opens in a new tab)Reviewed 1 November 202639 issues · 88 checks

This review found 39 issues worth fixing on bauerfeind.us, 13 of them high impact, across 88 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
3.4 s3.1 sMay 9Oct 243.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.3 s
Oct 10, 20263.3 s
Oct 17, 20263.4 s
Oct 24, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
105 ms104 msMay 9Oct 24104 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026104 ms
May 16, 2026104 ms
May 23, 2026104 ms
May 30, 2026104 ms
Jun 6, 2026105 ms
Jun 13, 2026105 ms
Jun 20, 2026105 ms
Jun 27, 2026105 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 2026105 ms
Aug 8, 2026104 ms
Aug 15, 2026105 ms
Aug 22, 2026104 ms
Aug 29, 2026104 ms
Sep 5, 2026104 ms
Sep 12, 2026104 ms
Sep 19, 2026104 ms
Sep 26, 2026104 ms
Oct 3, 2026104 ms
Oct 10, 2026104 ms
Oct 17, 2026104 ms
Oct 24, 2026104 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 bauerfeind.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bauerfeind.us at 1.0 s1.0 s
  2. bauerfeind.us at 2.0 s2.0 s
  3. bauerfeind.us at 2.9 s2.9 s
  4. bauerfeind.us at 3.9 s3.9 s
  5. bauerfeind.us at 4.9 s4.9 s
  6. bauerfeind.us at 5.9 s5.9 s
  7. bauerfeind.us at 6.8 s6.8 s
  8. bauerfeind.us at 7.8 s7.8 s

Speed

11 to fix46
  • Improve image delivery

    1.1 s · 4.4 MB

    19 images could be 4.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.1 s faster on a phone.

  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 5.1 s

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

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    900 ms · 169 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Accessibe Accessibility Overlay, Crazy Egg and Facebook and others), adding 715 KiB and 947 ms of main-thread time.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    368 KiB

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

  • Accessibe Accessibility Overlay adds 268 ms

    268 ms

    Accessibe Accessibility Overlay costs a phone 268 ms of main-thread work and 243 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.

  • 1,732 HTML elements

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

  • Font display

    250 ms

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

  • Legacy JavaScript

    115 KiB

    Polyfills for old browsers add 115 KiB JavaScript that modern phones do not need.

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 59 ms

    59 ms

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

Core Web Vitals

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

  • Time to Interactive: 35.5 s

    35.5 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “bf-us-compression-wear_banner-shopware-2”.

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0.031

    0.031

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

Images and page weight

4 to fix43
  • Page weight: 8.1 MB in 180 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 180 requests on a phone: images 6.0 MB (38), scripts 1.7 MB (102) and stylesheets 196 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 20 images in older formats

    20 images (1.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.

  • 10 images below the first screen load straight away

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

  • 4 images far larger than shown

    252 KiB

    4 images are downloaded at several times the size a phone draws them, for example knee-bodypart.jpg at 1,000 px wide, shown at 277 px. Resized copies would save about 252 KiB.

  • About 2.3 g of CO₂ per visit

    2.30 g

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

Accessibility

7 to fixGoogle 8592
  • Hidden but focusable

    8 elements hidden from screen readers can still receive keyboard focus.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • SVG elements with an img role do not have an accessible text alternative

    SVG elements with an img role do not have an accessible text alternative (1 element).

2 checks passed
  • Every image has alt text

    All 39 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 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 structured data

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

  • 4 links with vague text

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

  • 142 internal links, 13 external

    The homepage links to 142 pages on bauerfeind.us and 13 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Bauerfeind offers premium medical braces, sports supports and sleeves as well as compression socks and insoles for acti…”.

  • One H1 headline

    Your main headline reads: “Bauerfeind”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Bauerfeind Braces, Supports, Socks & Sleeves”.

  • Canonical URL set

    The canonical URL is https://www.bauerfeind.us/.

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

  • XML sitemap found

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

Other pages

100
  • 9 pages slow to respond

    https://www.bauerfeind.us/shop, https://www.bauerfeind.us/knee-braces, https://www.bauerfeind.us/ankle-braces, https://www.bauerfeind.us/elbow-braces-arm-sleeves, https://www.bauerfeind.us/back-braces and https://www.bauerfeind.us/calf and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 94 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 7370
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5213398&tm=gtm002&Ver=2&mid=8a9165b9-dc8f-4826-a24e-fe90bc9ae3ca&bo=2&sid=9859cce0d5c211f188485f0ddc43f635&vid=9859df60d5c211f1bf5b4942df4a52ca&vids=1&msclkid=N&pi=918.

  • 17 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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 410 ()”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • Thin social proof

    Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • About 568 words of copy

    The homepage carries about 568 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Sign up”, “Shop” and “sign up”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Hotjar and Meta Pixel and 3 mores (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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 bauerfeind.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on bauerfeind.us, including 19 speed issues, 2 SEO issues and 1 conversion gap. 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