item24.com website review

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

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

Reduce initial server response time. Google estimates savings of 1.1 s on a phone.

The HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

8 third-party services load with your homepage (Clarity, Cloudinary and Google Tag Manager and others), adding 3.7 MB and 1.6 s of main-thread time.

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

17 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

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

Cloudinary costs a phone 485 ms of main-thread work and 3.0 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.

Clarity costs a phone 592 ms of main-thread work and 28 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 349 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Your server takes 1.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

Your homepage downloads 5.4 MB in 189 requests on a phone: scripts 2.6 MB (74), images 2.1 MB (33) and fonts 352 KiB (9). Under 2 MB keeps phones on slow connections fast.

banner-neuheiten2026-II-1920x600.8d1d4329.webp 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).

1 image is downloaded at several times the size a phone draws it, for example banner-neuheiten2026-II-1920x600.8d1d4329.webp at 1,920 px wide, shown at 390 px. Resized copies would save about 45 KiB.

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

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

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

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 42 pages on item24.com and 11 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.

/en-us/categories/b3a9703f-4aa0-4f21-95ab-e9cbf3605534, /en-us/categories/4b18639f-a049-4ed5-a4ef-3342c4d3a26c, /en-us/categories/3daa5411-d50f-4f06-9696-67470dce8163 and /en-us/categories/ad64841a-3fa0-4051-bbe9-938da1c0989a have no <title>, so Google invents the link text in results.

/en-us/categories/b3a9703f-4aa0-4f21-95ab-e9cbf3605534, /en-us/categories/4b18639f-a049-4ed5-a4ef-3342c4d3a26c, /en-us/categories/3daa5411-d50f-4f06-9696-67470dce8163 and /en-us/categories/ad64841a-3fa0-4051-bbe9-938da1c0989a are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/en-us/categories/b3a9703f-4aa0-4f21-95ab-e9cbf3605534, /en-us/categories/4b18639f-a049-4ed5-a4ef-3342c4d3a26c, /en-us/categories/3daa5411-d50f-4f06-9696-67470dce8163 and /en-us/categories/ad64841a-3fa0-4051-bbe9-938da1c0989a have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 11 pages by a URL that isn't their canonical one, for example /en-us/categories/bbf42e66-b26b-4912-9200-719c117299eb, whose canonical is /en-us/shop/new-products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/en-us/categories/b3a9703f-4aa0-4f21-95ab-e9cbf3605534, /en-us/categories/4b18639f-a049-4ed5-a4ef-3342c4d3a26c, /en-us/categories/3daa5411-d50f-4f06-9696-67470dce8163 and /en-us/categories/ad64841a-3fa0-4051-bbe9-938da1c0989a have no <h1> headline, so visitors and search engines get no clear main topic.

/en-us/categories/bbf42e66-b26b-4912-9200-719c117299eb, /en-us/categories/46e41ed4-24ca-4d3b-93c3-cab05f69643c, /en-us/categories/19722987-b11b-4c32-a4e3-105f5674a6ca, /en-us/categories/7fd054a0-58df-4e34-bc27-9a6370954540 and /en-us/categories/c7810c3e-f947-4300-a605-418626faa081 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/en-us/categories/d2d35650-9962-4521-b67f-a6b6266786f4, /en-us/categories/46e41ed4-24ca-4d3b-93c3-cab05f69643c and /en-us/categories/42aebed3-ab38-4b34-a0e4-3f6143da7a0e took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.item24.com/en-us.

Large scripts ship without source maps.

1 link from your homepage to your own site is broken, for example https://www.item24.com/en-us/company/local-partners (404).

http://item24.com does not redirect to https, so some visitors land on the insecure version.

1 link to other sites is dead, for example https://welcome.item24.us/trainings (404).

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

Opening https://item24.com goes through 2 redirects before the homepage loads.

2 links go through two or more redirects, for example https://www.item24.com/en-us/cart/.

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.

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

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

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

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

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=_spf.item24.com”.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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

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