abcr.com website review

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

Your mobile performance score is 76 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

4 third-party services load with your homepage (Google CDN, Usercentrics CMP and Google Tag Manager and others), adding 1.5 MB and 768 ms of main-thread time.

About 778 KiB of JavaScript is downloaded but never used on this page.

Google CDN costs a phone 503 ms of main-thread work and 1.1 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.

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

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

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

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

259 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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 18.7 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 3.8 MB in 378 requests on a phone: scripts 2.3 MB (277), other files 729 KiB (26) and HTML 326 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example gebinde_footer.png at 1,440 px wide, shown at 390 px. Resized copies would save about 21 KiB.

1 image (61 KiB) is 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 further down the page (61 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (1 element).

Your title is only 27 characters: “AB677036 – abcr Gute Chemie”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 1 characters: “.”. 70 to 160 characters is enough to sell the click.

Open Graph is missing og:description, so shared links fall back to guesses.

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

The homepage links to 75 pages on abcr.com and 4 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.

/, /de_en, /de_en/stores/store/redirect/___store/de_de/___from_store/de_en/uenc/aHR0cHM6Ly9hYmNyLmNvbS9kZV9kZS8%2C and /de_en/stores/store/redirect/___store/de_fr/___from_store/de_en/uenc/aHR0cHM6Ly9hYmNyLmNvbS9kZV9mci8%2C all use the title “AB677036 – abcr Gute Chemie”. Search engines can't tell which page to show for a search, so each competes with the others.

/de_en/products/material-science has no meta description, so Google writes the search snippet from whatever text it finds.

/de_en, /de_en/stores/store/redirect/___store/de_de/___from_store/de_en/uenc/aHR0cHM6Ly9hYmNyLmNvbS9kZV9kZS8%2C and /de_en/stores/store/redirect/___store/de_fr/___from_store/de_en/uenc/aHR0cHM6Ly9hYmNyLmNvbS9kZV9mci8%2C use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /de_en, whose canonical is /de_en/catalog/product/view/_ignore_category/1/id/8539066. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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

1 error was logged to the browser console while the page loaded, for example “jQuery is not defined”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

3 links go through two or more redirects, for example https://abcr.com/de_en/stores/store/redirect/___store/de_de/___from_store/de_en/uenc/aHR0cHM6Ly9hYmNyLmNvbS9kZV9kZS8%2C/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

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.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Your longest form asks for 17 fields (0 required). Every extra field lowers completion.

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 318 words of visible text.

DMARC is set to p=none, so mail pretending to be abcr.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Google Tag Manager (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 13 cookies (measured from a US location before any click).

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