igus.pl website review

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

8 images could be 560 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, piwik.pro and survicate-cdn.com and others), adding 1.5 MB and 1.0 s of main-thread time.

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

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

Google Tag Manager costs a phone 609 ms of main-thread work and 1,003 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.

piwik.pro costs a phone 278 ms of main-thread work and 188 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.

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

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

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

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.

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

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

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

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

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

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

Real visitors wait 373 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

15 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-17, real Chrome visitors' tap response (inp) went from 455 ms to 498 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.7 MB in 122 requests on a phone: scripts 2.0 MB (45), images 1.2 MB (36) and fonts 150 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example FL_icon 1.c0f82bbd.webp at 1,424 px wide, shown at 126 px. Resized copies would save about 50 KiB.

3 images further down the page (138 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Some list items are not inside a list.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 444 pages on igus.pl and 30 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

/drylin/round-shaft-guide and /drylin/square-bearing-linear-guide all use the title “Prowadnice liniowe o profilu okrągłym drylin® firmy igus®”. Search engines can't tell which page to show for a search, so each competes with the others.

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

Your homepage links to 10 pages by a URL that isn't their canonical one, for example /drylin/profile-rail-guide, whose canonical is /drylin/w-slides. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=5525208&Ver=2&mid=2689282a-db97-4a18-ab6f-90de3cc823f8&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Usprawnij%20swoj%C4%85%20technik%C4%99%20z%20motion%20pl.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

2 links to other sites are dead, for example https://karriere.igus.de/category/einkauf-finance-hr/b7b9434e-5f37-5389-a7c9-890b467b809c (404).

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

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

2 links go through two or more redirects, for example https://www.igus.pl/iproSvc/appredirect.aspx?app=koplaitools.

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.

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

igus.pl'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.

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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 2,810 words of visible text.

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

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.