babor.com website review

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

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

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

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

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

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

6 images could be 507 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

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

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

Facebook costs a phone 316 ms of main-thread work and 280 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 block the main thread while loading, the longest for 339 ms. During a long task the page ignores taps.

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

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

9 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

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

Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

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

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

Your homepage downloads 14.4 MB in 259 requests on a phone: media 8.9 MB (2), scripts 3.4 MB (129) and images 1.3 MB (35). Under 2 MB keeps phones on slow connections fast.

babor-soul-body-collection.png 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).

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

14 tap targets are too small or too close together to hit reliably with a finger.

7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 15 pages on babor.com and 0 external pages.

There is no /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.

/products/soul-body/line/32005 has no <title>, so Google invents the link text in results.

/products/soul-body/line/32005 has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /products//65784-collagen-peptide-booster-cream.html, whose canonical is /products/doctor-babor/lifting/65784-collagen-peptide-booster-cream.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/shop/bestsellers, /promotions/gift-guide, /products/soul-body/line/32005, /products/fluids-fp/66140-advent-calendar.html, /products/cleansing/65944-milky-ceramide-toner.html and /products/doctor-babor/regeneration/65682-the-cure-mask.html and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

1 link from your homepage to your own site is broken, for example https://us.babor.com/cdn-cgi/l/email-protection (404).

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 540 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 5 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

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

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