bijou-brigitte.com website review

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

About 272 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.3 s.

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

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

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

21 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

8 third-party services load with your homepage (Nosto, getflowbox.com and adsdefender.com and others), adding 11.0 MB and 222 ms of main-thread time.

Vimeo costs a phone 0 ms of main-thread work and 10.8 MB 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.

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

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

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

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.

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

Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ein Mann und eine Frau tragen eine goldene Kette mit Buchst…”.

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

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

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

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

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

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

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

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

5 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 148 ms to 167 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.0 MB in 117 requests on a phone: media 10.8 MB (4), images 3.1 MB (77) and scripts 729 KiB (13). Under 2 MB keeps phones on slow connections fast.

Edelstahl_400x280px-2x-Skalierung.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).

12 images (1.0 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.

6 images are downloaded at several times the size a phone draws them, for example 110582516_1_tb.webp at 1,200 px wide, shown at 210 px. Resized copies would save about 271 KiB.

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

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

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

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

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

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (8 elements).

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

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

The homepage links to 267 pages on bijou-brigitte.com and 0 external pages.

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.

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.

/waterproof is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/wishlist has no meta description, so Google writes the search snippet from whatever text it finds.

/schmuck/ketten/personalisiert, /wishlist, /hochzeit, /inspiration and /inspiration/trends/dark-romance have no <h1> headline, so visitors and search engines get no clear main topic.

/neu, /schmuck, /accessoires, /waterproof, /schmuck/herrenschmuck and /neu/trending and 3 others took over 3 s to send their HTML from our server.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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

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

bijou-brigitte.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

bijou-brigitte.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,208 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.

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

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.

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