ahrend.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Intercom and Usercentrics CMP and others), adding 20.1 MB and 655 ms of main-thread time.

mediabank-collection.com costs a phone 0 ms of main-thread work and 19.3 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.

Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

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

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

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

3 images could be 224 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 74 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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

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

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

1 image 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 107 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 20.6 MB in 96 requests on a phone: media 18.9 MB (4), scripts 966 KiB (37) and images 463 KiB (29). Under 2 MB keeps phones on slow connections fast.

2 images (305 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 further down the page (229 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 5.85 g of CO₂e: 701.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

Your title is only 29 characters: “Ahrend. Vitalising workspaces”. 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 29 characters: “Ahrend. Vitalising workspaces”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 130 pages on ahrend.com and 5 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.

robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/ and /en all use the title “Ahrend. Vitalising workspaces”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/en/media-bank has no meta description, so Google writes the search snippet from whatever text it finds.

/en/products/webshop, /en/products/office-seating, /en/products/office-seating/office-chairs, /en/products/office-seating/standing-aids, /en/products/office-seating/counter-chairs and /en/products/seating and 5 others use the same meta description. A description written for each page earns more clicks.

/en has no <h1> headline, so visitors and search engines get no clear main topic.

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

21 of 75 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 “Failed to load resource: net::ERR_FAILED”.

5 links from your homepage to your own site are broken, for example https://www.ahrend.com/en/ (404).

HSTS is set, but max-age is 30 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.

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

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

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

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

DMARC is set to p=none, so mail pretending to be ahrend.com is still delivered. Reports are on, so moving to quarantine is the next step.

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

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